Skip to content
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

:PossessionSave only saves session after root directory #2

Closed
zeitchef opened this issue Apr 3, 2022 · 1 comment
Closed

:PossessionSave only saves session after root directory #2

zeitchef opened this issue Apr 3, 2022 · 1 comment

Comments

@zeitchef
Copy link

zeitchef commented Apr 3, 2022

Perhaps I'm not understanding exactly, but I would expect :PossessionSave to save a session with the name of the current directory, not the root directory.

Screen Shot 2022-04-03 at 22 33 24

Currently, this is the only session file it will create.

When I dismiss the message, I get the following error:

Screen Shot 2022-04-03 at 22 36 17

Edit: After actually looking at the commands, I realize this requires an argument. However, when saving the session, all open buffers are closed. Very weird.

I was hoping this would be essentially a drop-in replacement for auto-sessions which basically just manages the sessions for me. I don't want to have to type commands or use Telescope to load a session every time. If in the future, Possession will just work out of the box like auto-session I'll be happy to have another look!

@jedrzejboczar
Copy link
Owner

Well, the interface in auto-session is a bit different from what I can see. With auto-session your session name is the current directory name. In possession when you invoke PossessionSave {name} you would use a descriptive name for this project (PossessionSave my-project) and the file is stored under session_dir (can be changed in setup). CWD will be stored in the file contents (not in file name).

Anyway, currently there is no feature for automatic session save/restore. I might add it in near future, as it seems like a nice feature to have, though I generally prefer explicitly specifying which session I want to load.

I opened #3 and will close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants