dot-emacs VS marginalia

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.

Check out marginalia[1]. Whenever you press M-x, it will pop up a buffer showing all the commands (with most recent ones on top) along with their keybindings and a brief description of what they do.

Embark[2] is also cool. It will show all the possible commands relevant to where the cursor is at that moment. I bind it to C-c a.

[1] https://github.com/minad/marginalia

Then there is Marginalia which is IMO essential

marginalia. Informative annotations for minibuffer completion candidates, co-written with u/minad-emacs.

Wow, interesting that my response is getting down voted. It seems not enough that I give away my work for free. Nevertheless I appreciate support from the community, as other Emacs package developers. The support is actually helpful. To clarify, publishing my configuration would translate into quite a bit of work, requiring separation of private and public bits.

marginalia for extra info in the minibuffer

There seems to be some problem with straight not correctly installing or updating compat. See these issues on Marginalia and Embark where straight seems to not install Compat.

Note that I contribute to Emacs core itself from time to time but the process is discussion-heavy and thus time consuming. If you are familiar with the completing-read API, you may know the annotation-function of completion tables. The name already tells that this function just adds annotations to the completion candidates. The Marginalia package (written by /u/oantolin and me) provides such annotations. A similar function is the group-function, which groups candidates in subsets and adds titles above the subsets. I wrote the patch which added this feature to Emacs. It is now supported by default completion, Icomplete, Vertico and maybe other UIs. The initial implementation was done in the earlier Selectrum package, and a little later in Vertico.

At the end of the year, I am happy to announce the stable Vertico 1.0 and Marginalia 1.0 releases. Vertico is a minimalist, yet flexible and responsive vertical completion UI. Marginalia provides helpful annotations for many completion contexts. Both packages have been solid for a while but I rather let things mature slowly. These releases finally put the stamp "stable" on these two packages. I expect the other members of the package suite to follow soon after. Both packages have been updated recently to support the newest Emacs 29 features. They are compatible with Emacs 27, 28 and the upcoming 29.

I) I started out trying to implement this using marginalia, like the consult commands, but quickly concluded that this wasn't the way to go here... please correct me if I'm wrong and there is more from these packages I could make use of. I also try to make use of as much of the citar codebase as possible, but have found it difficult so far: a lot seems too specific for bibliographic entries.

I can't find anything that seems to discuss them in detail, but Marginalia is a package that applies them widely in completion. And here is a simple example for customized file completion.