-
Notifications
You must be signed in to change notification settings - Fork 24
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
Minimap breaks :mksession
#192
Comments
Could this problem be solved by toggling the minimap closed before you make the session? |
I don't see an autocmd in the documentation that fires when Without an autocmd, you might look into making a custom mapping or function that closes the minimap, calls mksession, then reopens the minimap. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I had this very similar issue based on what I see in Session.vim.txt |
I guess i have the same problem here aswell 🙈 minimap-breaks-with-syntastik-2024-11-30_18.38.34.mp4Do tell if i could provide anything meaningful. I have no idea and my Package Maintainer (Debian) has no either..Or rather he's too lazy ^_^ |
Check list
Environment info
Version info
Question / Problem and steps to reproduce
When using Minimap with
auto_start
, the command:mksession
will also save the minimap window with its "filename"-MINIMAP-
which will make loading the session file fail as Minimap will auto-start too when reopening the files from the session and thus try to open a minimap window with the same name as the one recorded in the session.Error Message:
Excerpt from Session.vim:
Full Session.vim:
Session.vim.txt
I believe Minimap should prevent Vim from saving its own windows in the session as they are unusable anyway since their contents are not stored in the file system. Even if untrue, it should at least provide an option to activate this in order to not break
:mksession
whenauto_start
is enabled.The text was updated successfully, but these errors were encountered: