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 underscores are an artifact of when this script used to be part of
the bash profile and I didn't want the variables to be exposed too much.
This is no longer relevant.
This makes the common actions previously encoded as bash aliases
independent of the shell (I'm using /bin/sh for the scripts), which will
make a potential switch to zsh easier by having less bash-specific stuff
around.
The substring expansion ${parameter:offset:length} is a bashism and does
not work when /bin/sh points to a shell other than bash, e.g. on Ubuntu.
This commit replaces this expansion with a call to awk, inspired by the
solution at:
https://wiki.ubuntu.com/DashAsBinSh
The solarize script evalss the output of the dircolors(1) but the
LS_COLORS variable gets exported in its environmnent, not the calling
shell where we actually need it so ls(1) and other programs wiill
inherit it.
Therefore, the evaluation of the dircolors(1) output is moved to the
change_bg() function in the shell, so that the LS_COLORS variable is
available to any children of the shell.
The reason why I had missed this is that in most systems I have ls
aliased to exa, which does not care about LS_COLORS and has its own
coloring system. On cygwin, however, exa is not available and I noticed
that the colors were missind; and indeed, on systems with exa the colors
are also missing if I run ls as \ls.
This makes installation a lot easier, as we just need to type:
stow -v dotfiles
instead of installing multiple packages and risking to forget something.
