-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with tmux-resurrect #16
Comments
Hi, looking into restore-vim-session code it seems to rely on the So there are 2 problems with implementing this using possession.nvim:
So this is harder to implement than it is when using the vim-obsession model. To implement auto-restoring of sessions you would need some way of knowing which session should be restored in which directory. Vim-obsession just checks if Then you would need to expose this in some convenient command so that it's possible to just call it from command line. Currently you can So integration with tmux-resurrect boils down to auto-loading, which has also been discussed in #3 and #12. I don't know what would be best approach to this, so I don't think I would be implementing this anytime soon. But if someone would like to implement auto-loading I'd be happy to help. |
Thanks for the reply @jedrzejboczar, I assumed it would be tedious to do given the way this plugin works. Glad to hear i'm not the only one looking for automatic session load/restore. |
tmux-resurrect is an amazing tmux plugin that allows your tmux sessions to be persistent after reboot. It has an amazing feature that allows you to also load your vim/nvim sessions afterwards as especified here restore-vim-sessions. Now the issue is when I restore my tmux session it attempts to automatically load all nvim sessions but for some reasons it can't. The feature requires that the corresponding session.vim are present in order to be able to load them. Hope anyone can reproduce the issue, thanks in advance. Sorry for opening the other issue 🙏. Amazing nvim plugin btw.
The text was updated successfully, but these errors were encountered: