gcmh VS GNU Emacs

cf. https://github.com/emacsmirror/gcmh (the author's [=Andrea Corallo's] Emacs package "GCMH - the Garbage Collector Magic Hack")

A lot of people use way higher values than 800 KB without any problems. As a matter of fact, I've been using 256 MB for a very long time, haven't noticed any issues with it. So I wouldn't call 1 GB madness, it can be perfectly fine in some cases, especially if one uses gcmh, so it has a high chance that GCs will happen when the user doesn't interact with emacs (I also setup emacs to do GC when emacs loses focus. This means that GC pause is invisible most of the time for me). I strongly prefer very rare, short GC pauses than microstuttering all the time. Also, some operations apply a lot of pressure to the memory system, and do hundreds of GCs with the default setting, so most of the CPU time is spent in the GC when these operations run. Increasing gc-cons-threshold makes such operations much faster which means less pauses.

One possible solution is to switch to a LSP approach. You should also take a look at the garbage-collector-magic-hack package: https://github.com/emacsmirror/gcmh

If you experience some lag, my first advice would be to install the GCMH package. It basically changes the garbage-collection rules to ensure that most garbage collection will happen in small bouts while Emacs is idle. After installing it I've never had my Emacs lag on me. This wouldn't address the retina-display issues you mentioned, but I've never experienced those with emacs-plus.

I've seen gcmh recommended as a library that configures the garbage collector for you. Not sure if it is truly a "one size fits all" solution though.

I’d add that for 1) beacon is a good package. For 2), this may be an issue where you have multiple emacs configuration files. This is a serious problem. 3) be patient, and use the magic GC hack. To add to that, you should probably set the GC threshold to be high. 4) projectile? 5)emacs -nw.

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):