more and more buffers in session files... how to clean-up?

[nnako]

Hi,

I often jump between projects by cd <project-path> which does the following:

• show a message "<num> buffers wiped out" with confirmation request
• load respective project session

Now, when changing projects very often, I have the impression as if, over time, the session files get larger and larger. Containing buffers from various projects in each session file.

Is it possible to some how "clean-up" the buffers and just keep the buffers currently opened within tabs / windows before saving the session files? Is there a respective parameter to be set?

Thanks.

[rmagatti]

Buffers should be getting killed upon restoring the new session. Is this reproducible between two cwd changes back and forth?

[nnako]

the effect is more like seen below (irrelevant information does not get removed over time but builds up). within a project configuration file (loaded when cd-ing into the respective folder) . this particular file is more than 900 lines long...

and further down within the configuration files there are hundreds of setlocal with some repeating parameter settings. I can not even remember to have set any of them.

maybe, you could point me to the location in code where these things are done?:

• update configuration file (choice of content, ...) - what is being written into the configuration file?
• trigger for config file write - when (based on which evebts) does a write of configuration files happen?

what would be the standard configuration file content structure?

[cameronr]

Just to make sure we know your config, can you share your auto-session config (or the output of :checkhealth auto-session)?

Assuming cwd_change_handling = true is in your config (which it sounds like it is), when you change directories auto-session will trigger loading the session for the directory being changed to, which you can see here:

https://github.com/rmagatti/auto-session/blob/main/lua/auto-session/autocmds.lua#L239-L277

The actual session is sourced here:

https://github.com/rmagatti/auto-session/blob/main/lua/auto-session/init.lua#L729-L756

All of that said, auto-session is using neovim's native session handling via mksession and then sourcing the created session when it's time to load it. What gets written to the session is controlled by sessionoptions'.

Once a buffer is loaded, it'll be saved as part of the session unless you close it, including buffers opened from something like lsp goto definition. Have you tried closing the buffers you don't think should be part of the session e.g. sumneko_lua.lua?

For repeated setlocal lines, those are options that are set on a per window or per buffer basis (as a result of having localoptions in sessionoptions), so more windows / buffers will likely mean more ’setlocal calls. The specific options set depend on your config and what other plugins you have installed; auto-session has no input or control over that at all as it's entirely controlled by sessionoptions and mksession.