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).
This is a preparation to start experimenting with zsh. The idea is to
share the aliases and environment setup between both shells to avoid
having a bunch of duplication. Even if I decide to stick with zsh it
would be nice to keep the bash configs around for systems where I might
not want to install zsh for some reason. We'll see how this goes...
Using the block cursor was hiding the character under the cursor because
I had set the cursor text color to the same as the cursor itself. This
commit fixes that.
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.
I was previously using relative paths to $PWD with the implicit
assumption that I would always run `bootstrap` from the dotfiles
root directory. This commit fixes that.
The links are only removed if they are broken and the target was within
the dotfiles bin directory. This makes it easier to deal with removed
and renamed scripts so I don't have to go hunt for them by hand.
Turns out C-b is quite useful for navigation in vim and other programs.
Also, the C-space issue seems to only happen when using Alacritty and
WSL, so I'll just avoid this combination for now.
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
