When I saved files in my eslint-formatted projects I was wondering about
slight differences between the results of running `eslint --fix` vs. the
autoamtic formatting when I save a file in neovim.
As it turned out I ran the wrong command indeed. This changes fixes that
by simply calling the correct command on save. Note that this looks
"bigger" but it's actually a copy of the built-in `LspEslintFixAll` of
neovim.
Reference: 1a6d692067/doc/configs.md (eslint)
Reference: 89fd0361b3/lsp/eslint.lua (L92-L104)
I do nearly all my mails with neomutt. So, I naturally edit mails with
vim (neovim to be precise). These settings add a couple of autocompletes
for very common mail-phrases. Furthermore I restrict the line-length of
my mails to 78 chars per line, since this is the recommended line-length
according to RFC-5322.
Reference: https://datatracker.ietf.org/doc/html/rfc5322#section-2.1.1
Many projects use markdown or asciidoc and write "endless" lines. That's
annoying on it's own, but not having them wrapped is even more annoying.
So, this change simply wraps these lines to make them more accessible
for me.
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.
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 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.
