cameronr
commented
1 month ago Thanks for the detailed report. The main question is how are you exiting nvim with unsaved edits in a swap file? Is it crashing for you or are you exiting in some other way? AFAIK, that should only happen in some significant error situation.
As for the error, it's happening while nvim is sourcing the session and happens on the edit docker/run_docker.py line. Because of the existing swap file error, nvim stops processing the rest of the session file (you can see that by doing echo g:SessionLoad and seeing that it returns 1. That shows it didn't get to the unlet SessionLoad at the end).
We rely on nvim's builtin handling of sourcing a session file so there isn't much we can do about that error. You can suppress swap file warnings by adding A to shortmess but that may make it harder to know if you have unsaved changes after a crash so only set it if understand the ramifications.
Separately, in your auto-session config, opts isn't being used because you defined a config function so none of the options set in opts are actually being used. If you want to use both opts and a custom config function, you have to add opts to the function definition and then pass it to setup like this:
return {
{
'rmagatti/auto-session',
dependencies = {
'nvim-telescope/telescope.nvim', -- Only needed if you want to use sesssion lens
},
opts = {
auto_session_suppress_dirs = { '~/', '~/Projects', '~/Downloads', '/' },
auto_session_enable_last_session = true,
auto_save_enabled = true,
auto_restore_enabled = true,
auto_session_use_git_branch = true,
auto_session_create_enabled = function()
local cmd = 'git rev-parse --is-inside-work-tree'
return vim.fn.system(cmd) == 'true\n'
end,
},
config = function(_, opts)
require('auto-session').setup(opts)
local wk = require('wk_mappings')
wk.wk().add(wk.auto_session())
end,
},
}OTOH, if you haven't needed those options, you could also just not set them. Also, auto_save_enabled and auto_restore_enabled are true by default so you don't have to set them true in your config.
Ben-PH
Describe the bug following error on startup:
coming after this message:
additionally, I use barbar, and it doesn't show up the loaded in buffers.
:bpand:bnwork, but jumping between numbered buffers doesn't. I'm not familiar enough with barbar to know how this might be relevant at a detailed level, but it supports an hypothesis that the feature of auto-session "reopening" the same buffers is not happening as expected.I run
:recoverafter all that, save, and the file is all good file-wise, but session is still corrupted, and need to manually delete the swap file. Once that's done, session opens as expected.If I open a session that isn't corrupted, and try to change to the corrupted session, the old sessions buffers do not close, and a single buffer of the opened session is opened.
this is the sessions file:
To Reproduce Unknown exactly, but this is my best guess:
Expected behavior
I select a swap-file option (recover, edit anyway, etc), and the session is restored, with the file(s) in question being opened to a buffer accordingly creenshots to help explain your problem.
Baseline (please complete the following information):
Result of
set sessionoptions?: sessionoptions=blank,buffers,curdir,folds,help,tabpages,winsize,terminalOS. e.g
uname -a: Linux LaptopOfTheseus 5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024 x86_64 x86_64 x86_64 GNU/LinuxNeovim version
nvim --version❯ nvim --version NVIM v0.10.1 Build type: Release LuaJIT 2.1.1713484068 Run "nvim -V1 -v" for more infoURL to your current config (if public)
not present, but here is the table I provide lazy.nvim for setup
-- bindings:
M.auto_session = function() return { { '', 'Autosession search', desc = "Session search", hidden = true },
{ '', 'SessionRestore', desc = "Session Restore" }
}
end