Even though it's required when on older vim versions, and I'm on neovim,
opening TypeScript files with FZF was borked. This fixes it.
Productivity ensues.
This stemmed from an issue where an older version of npm wasn't properly
resolving git:// repos as well as github-style dependency names.
Don't think it'll cause any harm to carry this around between my rigs.
In an effort to reduce the amount of manual lifting being done, I'm
finally coming back around to using a plugin manager for [n]vim.
Also formally swapping `vim` references for `nvim`.
Only checking for commands that are USED by the installer and not the
ones utilized within the dotfiles themselves. Since fzf has a sourced
file in the zshrc, it'll bark if that's missing already.
Same deal as fzf, moving away from installing these things as part of
the installer and favoring a version installed by the operating system's
package manager
My dotfiles rarely change, but the plugins and apps I use have regular
updates. I don't refresh my local dotfiles frequently, so it makes sense
to favor moving these things out of my installer and let the operating
system's package manager handle keeping them up to date.
Also left some notes for later when I get my new MBP.
Quite a few updates to leverage GNU `stow` and reduce the manual efforts
in the install script. Localized my `[n]vim` color scheme of choice
since it hasn't been updated in years. Also updated the installer to
pull from remote instead of completely removing itself if it's already
present.
Contemplating moving to using some plugin managers for `zsh` and
`[n]vim` to help reduce the install size a bit more, and to provide a
bit more flexibility for anybody else running this.
I don't use nvm version often outside of my work machine, so I like to
keep my prompt speedy by lazy loading it. With that, on my work machine,
I often forget to manually run nvm and that causes me more grief when
I'm trying to run something that had it's dependencies installed by the
older version.
Sadly, with installing an older version of Node.js on Arch, you don't
get the paired version of npm which caused it's own set of additional
problems for me. Ideally, once our local dev stack is fully dockerized,
I can go back to lazy loading nvm or just dropping it entirely since it
won't be necessary at all.
At this point, I always install / use zsh, so there's no point in
keeping this around just for the sake of thinking that maybe somehow
I'll do back to bash. If that day comes, I'll port my zshrc back to
bash.
