dot-emacs VS emacs-which-key

For example, I don't know what "vertico, consult, embark, marginalia, and orderless" is exactly, they're not part of my setup and I guess I don't want them to interfere with it.

You can find further optimizations on https://github.com/novoid/dot-emacs/blob/master/config.org when searching for "mode-line".

You're looking for org-expiry and its (org-expiry-insinuate) as you can see in my config: https://github.com/novoid/dot-emacs/blob/master/config.org

You don't have to repeat yourself; it is more about how you write. Literate programming lets you mix different languages as well as text and the code. Check for example Karl Voits. The only remark I can make is that some defvars don't need the comments, since they are written as self-documenting code. For example, 'large-file-warning-threshold' certainly does not need a comment which basically repeats what the name says, but that is not so unusual to see even amongst programmers sometimes.

For the very same reason, I started to use hydras: https://github.com/abo-abo/hydra - see my config at https://github.com/novoid/dot-emacs/blob/master/config.org

The same configuration using Emacs 27.1 also does not have this weird behavior.

Maybe somebody has an idea what I might change in my large setup in order to get rid of this issue ...

For linking to contacts, I started to use a custom link contact: which I don't use any more since I've found org-super-links which enables me to link to any heading quite fine including contacts.

My personal notes on any task or project are way more verbose than the information curated in shared business environments. I therefore invest work and keep a local Orgdown structure and sync a subset of information manually. I define custom links to Jira, emails, and all other external sources to keep links from my Orgdown files to everything else. This way, my only truth is within my personal knowledge management which simplifies search.

My personal approach is a static list of Orgdown files within a single directory (with very few exceptions) and a manually curated list of agenda files.

I think which-key already solves exactly that: https://github.com/justbur/emacs-which-key

As for the "complicated keybindings general" -- I assume because remembering things like C-x C-s is hard because of the shifted keystrokes? I get that, and there is in fact a solution for less used keybindings which I love, called 'which-key' https://github.com/justbur/emacs-which-key

I would recommend installing the which-key package, which is a fantastic discoverability aid. If you ever want an example config to get some inspiration, I have one here: Emacs Bedrock

Make sure you have which-key installed and turned on. When using a keybinding that has a prefix (like C-x or C-c), it displays all the keybindings that start with that prefix.

which-key for the shortcut menus

there are some packages to help with the keybings, which-key shows a list of keybind and its command and (guru-mode)[https://github.com/bbatsov/guru-mode] enforces to use the "best" keybind, for exemple, it forces you to use C-n to move the cursor, blocking you to use the down key, and if you press the down key, it show a text in minibuffer to the best keybind.

Thanks for confirming, I think it's an issue in which-key itself: https://github.com/justbur/emacs-which-key/pull/166

If you haven't already, definitely check out the package which-key.

> even though I'm a terminal user ... I really like the discoverability of GUIs, and that's where a good GUI is unbeatable by CLI.

CLI has poor discoverability? Sure; but even on the terminal, discoverability can still be good:

A couple of nice examples of discoverability in keyboard-focused programs:

- emacs' which-key[0]; there's a vim port[1] too. This shows you (some) of the available keybindings for the next input, and a short label. So you don't have to remember what `SPC h p ...` or all the options under `SPC f...`.. but it still helps to recall that `SPC h` is for 'help' related commands, `SPC f` for file related commands.

- emacs' magit[2][3]. Magit is so good at discoverability, that I'd rate it as the best tool for using git with. I've learned more about git from using it.

[0] https://github.com/justbur/emacs-which-key

[1] https://github.com/liuchengxu/vim-which-key

[2] https://magit.vc/

[3] https://emacsair.me/2017/09/01/magit-walk-through/

Am I right in thinking this is quite similar to which-key?