Closed amadeus closed 8 years ago
Oh, well. Bookmarks are registered as normal files, so :edit ~/Development/discord/discord_app
is executed and afterwards the user options are checked, session_autoload
in this case.
I'll see how to fix this properly. Thanks for reporting!
Maybe just a new section called startify_folder_bookmarks
or something?
or it could be like, startify_project_bookmarks
or something. Then existing functionality isn't messed with
It should work now!
Awesome, works great, thanks!
I have noticed a small, but kind of annoying bug, and I've been able to isolate the issue to being caused by Startify.
For reference, I have the following vim configuration related to sessions and Startify:
Lets assume for the example of this scenario that I have a session stored in
Session.vim
inside the first bookmark. I only have one file open in that session, if I do:ls
I get the following output:Everything looks good. If I close vim, and open a new vim, cd into that directory manually, run
:source Session.py
and then run:ls
again, the output is exactly the same.However, if I close vim, and select that Startify bookmark it appears to restore the session properly, however, if I run
:ls
I get the following output:It appears to create a sort of phantom directory buffer before restoring the session.