: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.
Vim automagically does some globbing, if a path to :edit contains
special characters.
Works: :edit /tmp/foo [bar]
Doesn't work: :edit /tmp/foo bar
This reverts 03de6ee but fixes the actual problem in another place by
throwing escape(xxx, ' ') at the path.
References #102.
On Windows with 'noshellslash', the 'dir' section would never show up due to the
unescaped backslashes in `cwd`.
escape() backslashes (if they exist) so that match() will pass properly.
See issue #52
In order to enable platform-agnostic patterns in `g:startify_skiplist`, as long as `shellslash` is set in a user's `.vimrc` before loading the plugin, patterns in `g:startify_skiplist` will work even if they use forward slashes.
The user has been warned and asked about how to proceed already.
Catching this exception removes the additional output afterwards:
Error detected while processing function <SNR>237_open_buffers:
line 38:
E325: ATTENTION
Closes#67.
In combination with certain plugins, the filetype wouldn't be set for
Startify, because a filetype was already set by another plugin in the
series of VimEnter autocmds.
Setting the filetype gets forced now.
