tabspaces VS bufler.el

tabspaces, the package that leverage vanilla emacs as much as possible by using tab-bar-mode and project.el added session/tabspace restoration somewhat recently and it works pretty well.

However, it seemed that the buffer save/restore was misbehaving. I created 2 PRs (one for save, one for restore) -- would you be able to have a look?

Hi all. I am using tabspaces: https://github.com/mclear-tools/tabspaces

I tend to use a single emacs instance and single frame with multiple tabs as workspaces using tabspaces (I'm the maintainer). That lets you group buffers by tab (which means by window configuration), and there is an option to connect tabs with specific "projects", as understood by the built-in project.el. I tend to have a tab for my agenda, another for email, and then tabs for whatever projects I'm working on. I've been doing this for a couple years and it works pretty well for me but YMMV.

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.