bufler.el VS GNU 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.

gnu.org - contains everything you need to research his philosophy.

stallman.org - personal website, contains a lot of opinion, but I absolutely respect this man in all what he says.

emacs.org (redirects to https://www.gnu.org/software/emacs/) - his non-philosophical work, one of two mainstream console text editors.

Forever, there was a file included in stock Emacs, `spook.el`, which could be hooked up to automatically add random strings of "interesting" keywords to each of your email or Usenet messages (in signatures, or in headers like `X-Spook`).

https://www.gnu.org/software/emacs/manual/html_node/emacs/Ma...

Looks like copyright date of 1988:

https://github.com/emacs-mirror/emacs/blob/master/lisp/play/...

https://github.com/emacs-mirror/emacs/blob/master/etc/spook....

Try `M-x spook RET` in an Emacs buffer.

If you want to spare a couple of detours, you probably could start with Emacs Org-mode according to Greenspun's eleventh rule: "Any sufficiently complicated PIM or note-taking program contains an ad hoc, informally specified, bug-ridden, slow implementation of half of Org mode."

Emacs: winget install GNU.Emacs

The whole cl-lib thing is a total disaster:

https://github.com/emacs-mirror/emacs/blob/master/lisp/emacs...

They added cl- as a prefix to each Common Lisp symbol.

FIRST is now called cl-first, CAAAR is now cl-caaar .

I would really prefer if GNU Emacs removes all Common Lisp functionality, instead of creating this really wacky stuff, with discussions about this topic every year.

Never too late to try! Take your time. Emacs will outlive us all. https://www.gnu.org/software/emacs/

GNU Emacs is a versatile, open-source text editor that offers extensibility and customization—a sort of self-documenting real-time display editor. Our thanks for the suggestion go to CartanAnnullator.

Emacs

Their DEFUN and DEFVAR macros for example let us define a function or a variable that will be available as a Lisp function, and can be used as an ordinary C function from the C code. Emacs is written in pure C99 language and works with both GCC and Clang I believe. We can just define a C function via macro, and it is auto exported and made available to Lisp. For example my first patch to Emacs was for this function (we added "count" argument to make it possible to skip enumerating files in a directory for the case when user code is just interesting if a directory is empty or not):