dot-emacs VS .emacs.d

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.

In my Helm, I have to actively choose the candidate to confirm it. So I can type in both paths that are shorter or longer then existing ones. I even made a video to demonstrate it, the thread was relatively recently up I think. My Helm setup is here it if helps you, find Helm in the list of packages.

I also use Helm, and I have no problems. Just keep typing, once you typed a letter that does not exist in a path name it will stop completing. I don't know if I have some special option enabled/disabled; I don't think you need it, but you can see my Helm config (just scroll down untill you find "Helm").

When all deps are installed,my config is over 200 packages. On my Arch Linux desktop I built in 2016, with i7 4.6k (haswell) it starts ~0.7 secs, but init time will be anything between 0.5 ~ 0.8 secs, i guess depending on what system does. So all things same, init time will vary.

I am using it in my literate org-config. If you scroll down, there is a big list of packages, and I have done a small wrapper around helm-imenu, to jump to a package configuration. Looks like this.

That does not work for completions, at least not for me. It works for keymaps, so you can have mode specific (or really any) keymap in src blocks. I have been using his method myself in my init file generator for quite a while now. If you (or anyone) knows/have an idea how to expand it for completions and eldoc, I would be really happy to hear.

I don't know what if it is more robust but I use more or less plain dired with just some options turned on to make it less noisy to look at, but I don't "manage" my files so much to be honest. I do use some extras from dired-hacks, and my own dired-auto-readme, but that is about it. You can check my setup if you wish, look at "dired" under packages and in Lisp folder for "dired-extras.el".

I personally put all custom lisp in a special directory and scrape autoloads myself. If you are curious, you can check under "generator", functions generate-autoloads and collect-autoloads, but there is nothing special, just plain text search and copy-paste programmatically. I don't recommend to use it though.