bufler.el VS dot-emacs

No problem, I know that time is limited. There have already been a couple of issues filed about TRAMP, e.g. https://github.com/alphapapa/bufler.el/issues/63 If you last tried Bufler before those issues were filed, maybe give it another try; otherwise, please do chime in on that one when you get a chance.

The package I've written that provides tools for grouping buffers into something like "workspaces" would be Bufler: https://github.com/alphapapa/bufler.el See bufler-workspace-mode. It has many more features which are described in its readme.

What are you trying to convince me about? :D :D :D. To start with I recommended to you to use ibuffer, and I can recommend you even to check up Bufler if you are heavy ibuffer user.

Bufler has a lot of options in how to group buffers: https://github.com/alphapapa/bufler.el

Others have mentioned the awesome projectile, but I think it should be said that Emacs now has built in project.el which has come in leaps and bounds (though probably still lacks some projectile features).

I use project.el alongside consult[1] which has many convenient wrapper functions over built-in ones, like an enhanced `switch-to-buffer` with project support. I am actually using an even tighter integration called consult-project-extra[2].

The most advanced and overkill solution would probably be to use bufler.el[3] which basically allows you to define your custom logic for buffer grouping.

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

[2] https://github.com/Qkessler/consult-project-extra

[3] https://github.com/alphapapa/bufler.el

It's not designed to work that way, but it's theoretically possible. Especially, when I refactor parts of Bufler to use Taxy, it will be easy to make certain grouping keys non-consuming. See https://github.com/alphapapa/bufler.el/issues/69

Regarding the buffer-switching part of this package, you might look at https://github.com/alphapapa/bufler.el and consider how you could implement it through Bufler.

See also https://github.com/alphapapa/bufler.el Its readme also links to related projects.

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.