[Info-vax] SET DEFAULT iterative logical name translation

[Lawrence D’Oliveiro]

On Wednesday, October 27, 2021 at 3:34:29 PM UTC+13, alanfe... at gmail.com wrote:
> So Emacs lets you put in key definitions in a readable file and you don't need to
> compile it into a huge section file and thereafter not be able to list your commands?
> If it does, that's cool! 

It’s all just a bunch of ELISP definitions. Your custom functions and commands can have docstrings as well, to integrate with the built-in help system.

Here is my current collection of public customizations: <https://github.com/ldo/emacs-prefs>.

> I've used emacs on occasion. A lot of two-keys-at-the-same-time commands. And often
> two of _them_ in a row. And the 4,5 bit bothers you on EDT? Here's an emacs key
> definition with three in a row!: C-x 4 C-o 

Less common commands take more keystrokes, more common ones (like the movement ones I mentioned) typically take fewer.

> And another problem I always had with emacs: Once you start a session for the first time
> in a long time, you can't figure out how to exit. Well, I'd always forget it after a while and
> have to look it up. You'd think it would be a single key, like Ctrl-X or something, but
> NOOOOOOO. It's C-x C-c ...

I tried for a while, binding it to a single custom keystroke. I removed that after I hit it by accident once too often.

The thing with Emacs is, just keep it running all the time. And also turn on its server mode. I have the following command defined in Bash:

    alias e='emacsclient -n'

So in any terminal session, I can just type “e «filename»” to have that file open immediately in the always-available Emacs window.

> Hey, if emacs works for you, that's great. Go for it. 

There are depths to it I haven’t explored yet. For example, the text-attribute and overlay features (there seems to be some overlap between the two). One of the things I have done with overlays is being able to collapse (hide) selected regions of a file.