Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy
by zrail on Friday August 06, 2021 @09:18PM
(#28094780)
Once you've hit C-x e once you can keep bouncing e to repeat the macro as well.
Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy
by anyfoo on Friday August 06, 2021 @09:46PM
(#28094926)
Thanks for the reminder. I knew that once, but completely forgot about it!
Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy
by frosted-flakes on Saturday August 07, 2021 @05:39AM
(#28097225)
Using non-standard notation for describing keyboard shorcuts doesn't help.
Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy
by anyfoo on Saturday August 07, 2021 @02:21PM
(#28100700)
This is the notation that emacs has been using forever, and also displays to the user, so every user should be well comfortable with it. It even says “Press C-x C-c to exit emacs” at startup.
Re:The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy
by frosted-flakes on Saturday August 07, 2021 @02:47PM
(#28100868)
It's still non-standard, and is yet another barrier to adoption.
If anyone reading this hasn't used keyboard macros in emacs, try it out the next time you do something repetitive. It's amazing how it can simplify those tasks. "C-x (" to start defining one, "C-x )" to end it, "C-x e" to run it, which conveniently also ends definition if you want to use it right away. Of course you can do things like "M-5 C-x e" to run it 5 times.
But I do get your point: Things are probably much less discoverable in emacs, unless you are relatively proficient in it already maybe. You need to switching into a "programmer" mind fairly quickly, while BBedit probably just lets you do powerful stuff through simple UI.