-
-
Notifications
You must be signed in to change notification settings - Fork 27
Is it possible to persist gina buffers in a session? #171
Comments
I think it's technically possible but difficult with a current implementation. If I remember the feature of mksession correctly, it creates a vim script file which opens existing buffers. While gina uses an alias name in a bufname for a particular git repository, users must call Gina command to open a buffer so that gina can make the alias. So if you modify the generated vim script by mksession manually, I think it's possible. Or if gina uses a full path of a git repository and global BufReadCmd to opens a buffer. I've been wondering such changes for the next version. However the change would have a lot of side effects so I don't have any plan for mean time. |
I was doing a bit of research into this and I was going to suggest this as well. I think that would be fantastic. Any reason why you didn't go in that direction from the beginning? (I love this plugin by the way! I hope I can contribute soon.) |
There are two major reasons.
Assume you have a git repository under /home/my/code/github.com/me/foo. Gina uses an alias repo name so the bufname of "Gina show README" on that repository would be "gina://foo:show/:README". I prefer this name rather than "gina:///home/my/code/github.com/me/foo:show/:README".
Assume that you hit "Gina grep -e hello --and -e world". |
What about a bufname scheme similar to neovim's |
Unfortunately no. The bufname must contain an absolute path for Containing all extra arguments in a bufname is one option. Actually, I was thinking it in that way but I haven't tried it so I'm not sure if it's globally (cross-platform) possible. |
I would like to persist
gina://
buffers in a session generated bymksession
. Is this possible?The text was updated successfully, but these errors were encountered: