You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In issue #19@diego898 reports the following two unrelated problems:
Things seem to be working although there is two slightly strange things:
The current directory on NERDTree is not saved with the session. It always starts on ~/myname/Desktop, the directory I make gvim start out of by the shortcut I use. Vim's cwd changes quickly however, due to things in my vimrc that makes its current directory match that of the open file.
Upon startup, both nerdtree and the file that is shown (correctly coming over from my last session which is good) are both shown at their very very bottom. In other words, a file with lines 1-30, starts with line 30 at the very top of my screen with vim showing me ~ for 70 lines? NERDTree also starts "too high" as it were. A quick gg fixes it, just found it a little strange.
Since these are new problems I'm closing #19 and using this new issue to keep track of them instead.
The text was updated successfully, but these errors were encountered:
The current directory on NERDTree is not saved with the session. It always starts on ~/myname/Desktop, the directory I make gvim start out of by the shortcut I use. Vim's cwd changes quickly however, due to things in my vimrc that makes its current directory match that of the open file.
This sounds like a bug, in which case it should be fixed. I'll take a look at the code to see if I can find anything amiss.
Upon startup, both nerdtree and the file that is shown (correctly coming over from my last session which is good) are both shown at their very very bottom. In other words, a file with lines 1-30, starts with line 30 at the very top of my screen with vim showing me ~ for 70 lines? NERDTree also starts "too high" as it were. A quick gg fixes it, just found it a little strange.
I've seen this problem before, on multiple platforms and multiple versions of Vim, but never got to the bottom of it. I'd like to get this fixed but currently wouldn't know how to fix it.
In issue #19 @diego898 reports the following two unrelated problems:
Since these are new problems I'm closing #19 and using this new issue to keep track of them instead.
The text was updated successfully, but these errors were encountered: