bufler.el VS torus

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.

The org roam notes illustrate well why I can't just add each file to something like torus individually -- I have hundreds of notes on literature and adding them all by hand would take forever. But I could write a function which would return, for each buffer, the relevant other file. Each lit not has an ROAM_REFS property, which holds the key for the literature in my bib file, and then ebib and citar have enough code that I could write a function for going from that to the pdf file. I would be happy to write that function, but I need a package to knit the whole thing together. It should lookup the right command for the right buffer and jump to it.

If you're looking for a newer implementation inspired by the idea of mtorus, you may want to give https://github.com/chimay/torus a try. Chimay is also active in this subreddit.