I assumed that every shell would support '&&'. Apparently this is not the case
for Fish: it uses 'and'...
Anyway, the simple solution is to avoid cd'ing in the proper directory first
and just using absolute paths for ln instead.
References #165.
This option forces the use of <nowait> mappings.
This might be useful if you have global mappings that start with the same
characters as indexes from Startify.
References #180Closes#186.
<nowait> guards against global mappings.
Problem: However, having 2 local <nowait> mappings, '1' and '11', makes no
sense, since it would always go with the former.
Solution: Remove <nowait> from all dynamically created mappings and keep it
for the fixed ones (i, b, v, ...).
If you absolutely need a <nowait> mapping for a non-fixed mapping, e.g. 'g'
(and because you use vim-commentary which maps 'gc'), see
":h startify-autocmd":
autocmd User Startified nnoremap <buffer><nowait><silent> g ...
References #180.
Reported-by: @noscripter
These files can be used to set up additional things for a session and have to
be placed in the same directory as the session file.
See point 10 under `:h :mksession` for more information.
Since they are no real session files, Startify shouldn't list them either.
Closes#179.
This sets all the created mappings as `nowait`, meaning having global
mappings will still allow you to jump to a file instantly.
For example, if you have a commentary plugin and define a global mapping
of `gcc`, you can't use `g` without waiting (or clicking Esc right
away).
Closes#180.
Originally this check was meant to prevent showing the Startify buffer for
certain cases I can't recall anymore.
Now the Startify buffer will be shown at startup if these conditions are true:
1) no arguments were provided to Vim on the commandline
2) the first buffer is empty
