I used zoxide wrong all the time... By simply initiating it correctly it
immediately get's smarter and better. Imagine you have a dir like this:
~/deep/level/nested/but-with-very-specific-name/xy11-with-many-more
Imagine further that in your current directory is nothing that starts
with `xy`, then you only have to enter `cd xy` and zoxide will figure
out that you meant the deeply nested complicated name and change the
directory to there! - How awesome is that!
So, keep in mind use zoxide correct and it becomes easy to use!
The most important change is that I no longer create completions for fly
and kubectl automatically. Furthermore the automatic creation of a
cronjob to empty the downloads-folder is also gone. - These
funtionalities better fit the initial dev-machine setup, so I gonna move
them over to there soon.
I finally made the switch from the bare-repository method to stow to
manage my dotfiles. This brings some nice benefits, e.g. I can savely
say what file is in my dotfiles and what is missing out. Furthermore the
usage is _way_ simpler the before. Though one downside is the more
complicated removal of files, but I've documented a way which feels nice
to me as well. Finally I removed my old setup-script since I switched to
an ansible-setup anyway. So this config will eventually be applied
ansible and I don't have to care about installed software in this repo
anymore!
Reference: https://www.gnu.org/software/stow/
Reference: https://news.ycombinator.com/item?id=11071754
Reference: https://gitea.nehrke.info/nemoinho/dev-machine/
On typical linux distros `lesspipe` is already shipped as part of less.
Though on macos it isn't, but I found out that it can be isntalled via
brew. So, I have no reason to not use and can savely ditch my custom
lessfilter.
Sometimes I have sensitive and system-specific configurations for bash
which I want to save. This change is a quick solution to enable this.
Maybe another solution involves a setup with encrypted secrets like
ansible handles secrets. I should evaluate such a solution in future.
