Assuming a small screen and 'wrap' set:
The cursor is forced to stay in a certain column, so doing gj on a wrapped
line will jump into an area outside the position [x] and jump back into it
immediately effectively breaking navigation.
Solution: use local mappings that just do the usual h/j/k/l dance.
References #156.
The skiplist gets checked against normal Vim regular expressions. That also
means that you can't just use '~'; see ":h /\~".
That especially sneaky if you use variables that refer to directories within
your home directory.
Solution: expand them via fnamemodify().
References #154.
With these settings: wildmode=list and laststatus=2
When call the command :SSave and use <tab> for autocomplete, and choose any
session, then the message "Session already exists. Overwrite? [y/n]" does not
appear on screen.
References #155.
fugitive is run at VimEnter and for new buffers that are associated with
files.
Now fugitive commands will be available after start (in the Startify screen),
but it won't work after calling :Startify, since fugitive is designed that
way.
References #33.
This de-duplicates the shared code, and adds some (first) improvements
to not stat all of v:oldfiles (twice).
If accepted, it allows for easily adding a cache for abs_path handling
etc.
- Add _show_filtered_oldfiles and _get_filtered_oldfiles
- Fixes g:startify_files_number<1
:mksession saves opened buffers and files listed in the arglist.
Assuming you would do:
$ vim foo bar
:SS session
:x
$ vim
:SL session
:bwipeout bar
:x
In that case the only file left in the session should be 'foo'. But
that's not the case, since :mksession! also saves the argument list,
which still consists of 'foo' and 'bar'. Next time you load the session,
both buffers would be opened again.
But since the argument list is seldomly used, or at least not with the
arguments that were given to Vim, it will be pruned from now on.
References #106.
