Can you turn off session saving when using MiniSessions.read()?

[KodyVB]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.sessions

Question

When I open a session and make some changes, whether it's opening new files or going to another part in the file, when I switch to another session with MiniSessions.read(), it saves my currently open session. Is there a way to turn off the auto-saving so if I go back to my first session it'll open as it originally was?

And sorry for the quick edits - I accidentally pressed enter in the title section and posted it early.

[echasnovski]

No, not at the moment I am afraid. It was the original behavior, but was changed in a050861, as I tripped many times when switching sessions. I assume that intentional leaving the session should autowrite it (at least if config.autowrite is true).

In theory, I'd say that it might be better to have read() autowrite current session only if config.autowrite = true.

Is it only a matter of personal preference to not autowrite current session when reading another or is there some particular use case or workflow that this is not aligned with?

[KodyVB]

I like to have the consistency of opening a lot of my sessions to points that I'm expecting in order to have a consistent experience. Like my nvim config session, I like to open to the start of my main init.lua with nothing else open. And there are multiple times where I've jumped into session X just to make a quick edit and jump back to session Y but didn't want to have X's session changed.

Currently, I find myself having to :qa and re-open nvim to avoid the layout changing, and in my case it's happening more often than I save the session intentionally. It might just be because that's how the first session manager I used did things, so I got used to the workflow.

[echasnovski]

I like to have the consistency of opening a lot of my sessions to points that I'm expecting in order to have a consistent experience. Like my nvim config session, I like to open to the start of my main init.lua with nothing else open.
...
Currently, I find myself having to :qa and re-open nvim to avoid the layout changing, and in my case it's happening more often than I save the session intentionally. It might just be because that's how the first session manager I used did things, so I got used to the workflow.

So as far as I understand, you have MiniSessions.config.autowrite set to false, correct? Otherwise, it would have saved the current state of the session (i.e. not only the 'init.lua' file, but also some other files opened just before :qa).

[KodyVB]

That's correct, I have it set to false.

[echasnovski]

That's correct, I have it set to false.

I see. Yeah, I think it is reasonable to have that auto-writing behavior inside read() only if config.autowrite is true. I'll take a look.

[echasnovski]

This should now be resolved on latest main: there is auto-write of current session in read() only if MiniSessions.config.autowrite is true. This indeed makes a more coherent behavior, thanks for mentioning this use case!