I barely have any file valled "vault.ini" or "vault.yml" except of in
the ansible context. So, this treat all these files as ansible-vault
files. The other change affects the way we're looking for an ansible.cfg
file. 1st we check if it's present in the current working dir, if it's
missing there we check if one exists in the same directory as the
vault-file itself. If we do not find any files then we give up and do
not decrypt/encrypt the vault-file. Note, that this also means that we
need an ansible.cfg for the vault to be encrypted/decrypted, no other
method is implemented.
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 struggle to remember certain shortcuts sometimes. In these cases I
rely on the "whichkey" plugin which shows a short description of for
each possible keystroke in vim. Though I was lazy and didn't maintain
these everywhere, so this change fixes that. Hopefully I can remeber all
the keys better now.
Furthermore this change contains some slight remappings regarding the
git-keymappings. I used fugitive for most of that in the past, but I saw
more potential using telescope in certain cases, especially navigating
the history.
I still do not get the right location to change these settings and on
each i3-restart (which I do regulary) the settings get set back.
Therefor I change them to be executed on _each_ restart.
I'd used custom shell-scripts for a while though since I saved them with
the exact same name as the actual program I confused myself. E.g. when I
tried to use rofi to provide me a dialog to choose from some options.
So, I discarded this approach :)
In case a file is moved to another location this change will most likely
end in a dangling link in the home-dir. This change fixes this by
removing links automatically which are off because the target-file has
been moved to another location.
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.
I struggled to distinguish between a simple key-stroke and a pressed
key, which should lead to repeat inputs. Initially I copied this value
from my macos-settings where I use the same keyboard, but it turns out
that the timing is somehow different.
Remember set this to 200ms on macos and 250ms on X11.
Note, I have no idea which one is more accurate, but since everything on
a mac feels (and is) slow I would guess linux is correct and apple lies.
