Closed rooday-doordash closed 1 month ago
I would frankly say that it is not the bug with the plugin itself. It is related to the distribution SpaceVim
.
@tan-wei I'm sure you're right, I'm just not sure where else to get info on this (pretty new to spacevim/vim plugins in general). I've noticed that spacevim is using this startify plugin which I think has it's own session handling logic, perhaps that is causing a conflict? Are there any known issues between startify and autosession?
Yeah this isn't really auto-session related. It just looks like the plugin never loaded if :SessionSave
is not available. I'm gonna close this issue until an actual problem with auto-session itself comes up. I don't personally use SpaceVim so this isn't something I've come across or would have the time to dig into unfortunately.
Perhaps posting on the SpaceVim repo would shed some light?
@rooday-doordash If the plugin is loaded correctly, these commands should be enabled. For example, if you lazy load the plugin without set events
or something else, it will cause the issue you descibed. Maybe you should ask Spacevim directly, to know how to load the plugin you add correctly.
Describe the bug Adding auto-session in SpaceVim init.toml doesn't seem to load the plugin.
To Reproduce Steps to reproduce the behavior:
:SessionSave
commandExpected behavior For the command to work/the plugin to have loaded.
Baseline (please complete the following information):
set sessionoptions?
:sessionoptions=blank,buffers,curdir,folds,help,tabpages,winsize,terminal
uname -a
:Darwin KMX5QH9Q0F 23.5.0 Darwin Kernel Version 23.5.0: Wed May 1 20:17:33 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6031 arm64
nvim --version
:NVIM v0.10.0
Here's my SpaceVim init.toml: