Since I use which-key I can actually benefit a lot from meaningful
descriptions of my custom shortcuts. Whenever I feel like I forgot a
multi-key shortcut I can simply type the first letter (in my case
usually "Space" or "g") and peek into the preview of whichkey. It lists
all possible additional keystrokes and their descriptions, so this
change makes it a lot easier for me to find the command I'm looking for.
When working in vim I have developed some pattern which fell fast and
confident enough for me to being typed all the time.
E.g. I catch myself often doing typing the following: `:Gw<CR>:G<CR>cc`
These keystrokes safe the current file directly to the staging area of
git (:Gw), then opening the fugitive-panel (:G) and finally letting me
write a commit-message form there (cc).
The keypart here is that I _have_ to open the fugitive-panel to perform
a commit, since I don't use any abbreviation for "commit" on git itself
the only other way is typing `:Gw<CR>:G commit` which is cumbersome.
This change allows me to type just another short version (namely:
`:Gw<CR>:Gc`) which saves 2 keystrokes and a whole panel-rendering.
Though this change is experimental right now since I don't know if I
really get used to it.
It took me some time to stumble over this mistake, but now I'm finally
able to create new directories directly from neomutt and get them
synched correctly to the IMAP-server.
Since I use G-Mail right now that frees me from creating labels for
everything since I can now freely move my mails through the directories
and the sync will create the labels automatically.
Btw. the default is mbox as stated in the docs.
Reference: https://neomutt.org/guide/reference#3-243-%C2%A0mbox_type
It is simply annoying to have sometimes "i" and always "q" to exit a
menu (view) in neomutt. Instead this change normalizes that by removing
_any_ functionality from "q", except of quitting neomutt on the index.
In turn "i" becomes the only binding to exit a menu.
This change improves actually 2 things for me, first the coherence and
second the "i" is actually easier to reach and therefore more pleasant
to exit quickly from the attachments then via "q".
I like gruvbox, because it improves the readability a lot!
Though the bare scheme does not match all my expectations, therefore I
added some more settings in the muttrc. The scheme itself came from the
official neomutt page.
Furthermore this change fixes the display of the date and the overall
preview to a easier to read format.
Reference: https://www.sthu.org/code/codesnippets/mutt-gruvbox.html
Some mails are just stupidly hard to parse, especially if the HTML
contains dozens of images. Kununu even managed to include the same
amount of images into the text-mails with all their marketing foo in the
URL. So, since these were so hard to understand I needed multiple
different "grades" of URL lists. This change allow be to choose between
different views.
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/
