On my machine, e is just a way to send things into Emacs.<p><pre><code> $ which e
e () {
snippet="(nkv-find-file-and-jump \"$1\")"
emacsclient --no-wait -e $snippet
}</code></pre>
can you confirm whether this is ai-written or human driven?
What is meant to be the selling point over Emacs? Apart from scheme>elisp?<p>Arguably 80% of the emacs goodness is the terabytes of elisp written in the last few decades, if you break compatibility with that you need to throw in something pretty compelling.
Chapter 12.2, Guideline 1: <a href="https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html" rel="nofollow">https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1...</a>
Program names should be between 2 and 9 characters; As a thing to consider. Also, searching for `e` may be weird.
What does self-aware even mean in this context?
Given the obvious AI vocabulary scattered through the README, I'm hoping it doesn't mean "self-aware" in the HAL sense.<p><pre><code> `C-x C-c`
I'm afraid I can't let you do that, $USER</code></pre>
M-x ?
For vi-heads: ":" The key combo that puts you into command mode. M is "meta", which is Alt on PC or Cmd on Mac.
These are all conventions and you can change them, but I'm used to Meta = Opt and Super = Cmd on macOS.
That is incorrect. In vi and vim, "ESC" is the key that puts you into command mode (from insert mode). Command mode is the full-screen visual mode where you enter commands by a sequence of keypresses.<p>":" is the key which issues "ex" commands. vi and ex are two different modes of the same editor. Any command which begins with a colon is an ex command, not a vi command, not done in "Command Mode".
True. ":" is the rough equivalent to M-x, though.<p>Also worth mentioning is Q , which puts you in ex mode, essentially just ":" prompts one after the other until you exit or issue a "vi" command to go (back) to visual mode.<p>And then there's open mode, but vim doesn't implement that.
That is what people use for the Alt key. I mean, I use Emacs daily, and I (mostly) like it. But the terminology *) is really fucked up inside Emacs.<p>Almost no one realizes that perhaps since 35 years no keyboard in mass-use had an "Meta" key. And if the "e" people now still keep that weird name, then they aren't similarly frozen in the state of time as the Emacs community.<p>1) There's more. Lisp still let bleed assembler instructions that no CPU used in the last 40 years, like CDR and CAR. That's if like e.g. JavaScript would have a cmpxchg() function.<p>also 1) Or it uses "window" in a very different sense.<p>and also 1) and even when the term is what you expect, they -- in best english tradition! -- can't normalize on one writing. You can e.g. find both "assoc" and "assq" in use.<p>So if you want an extremely powerful editor construction kit with an extremely weird nomenclature of parts of it, then chose Emacs.
M-x doctor