The reason for this is that in some servers the automatic detection (see
:help background) is guessing it wrong and using a light background,
consequently burning my eyeballs every time I open vim.
Hard coding the dark background seems fine for now, as I seem to never
really have a need for the light version. If the needs arises in the
future, then I'll have to come up with a better solution, but KISS for
now.
I actually don't have a use case for this at the moment and removing it
avoids running arbitrary vimscript unintentionally. I can always add it
back later if a real world use case arises...
The end sequence was undefined and messing up everything. I took the
opportunity, while fixing it, to tweak a bit the colors themselves and a
definition for blinking text matching bold text.
The reason for this is so that I can link from the home directory to the
files into ~/.config for files that need to be in the home directory
(e.g., .bash_profile, .zprofile, .jupyter/*, etc.)
The leading comma seemed like a good idea to namespace my commands but
in practice in turned out to just be annoying and not provide any real
benefits. So down with the comma...
Going back to the alias solution, which works for both bash and zsh, to
avoid having to search through the path for the real tmux after I remove
the leading comma from my custom command names.
Instead of wrapping man (1), I just export the LESS_TERMCAP_* variables
into the environment. This achieves the same thing as the wrapper
script, with the added benefit that less (1) will use the configured
colors in any of its invocations, not only via the wrapper script.
The reason is that neovim might be installed in one of the paths added
during the manipulation (e.g., for some reason neovim was installed
under ~/.local/bin).
