4 ms·

Right? And yet I just typed 'emacs tutorial' into DDG, and the first three results all hit you right away with descriptions of keys that don't physically exist

Right? And yet I just typed 'emacs tutorial' into DDG, and the first three results all hit you right away with descriptions of keys that don't physically exist on a modern keyboard. https://www.gnu.org/software/emacs/tour/ https://www.gnu.org/software/emacs/tour/ http://www.jesshamrick.com/2012/09/10/absolute-beginners-guide-to-emacs/ http://www.jesshamrick.com/2012/09/10/absolute-beginners-gui... https://www2.lib.uchicago.edu/keith/tcl-course/emacs-tutorial.html https://www2.lib.uchicago.edu/keith/tcl-course/emacs-tutoria... I've never tried emacs in large part because I've been convinced over the years that the various combinations of keys I would need to memorize are too complicated. I just did that search thinking that maybe I'd been mis-remembering, but no, that's still the impression that I have.

1ark 7y ago
I'm curious, how do you remember key combinations in other IDEs? I learned Vim, it was tough, but I remember a handful of commands I use all the time. And used Vim mode when available in IDEs when available. Spent a few years with VS Code, but I could never remember certain keys to navigate between panels for example. But the F1 key is great though. For w/e reason, I tried Emacs with evil-mode. I don't have to remember that many new keys I think, but a few of course. 'which-key' and M-x enables me to search for all commands, and I can also see the key combinations if I need to learn it later. In VS Code I try the F1 key, but if I could not find it there, I would grab the mouse and click around in menus looking for key combinations. Or go into settings and try to find w/e I was looking for. Of course, in Emacs I have spent hours setting things up, searching on the internet for clues on how to get something working as expected. Perhaps I am doing something non-optimal in my process. Curious how others learn/get productive in their respective IDEs.
- pwinnski 7y ago
  In most IDEs, they're the same key combos I use in non-IDE products. I'm on a Mac, so Cmd-X, Cmd-C, and Cmd-V work pretty much everywhere. They even work at a terminal prompt, and the latter two work in vi. I did learn vi years ago, but I'm sure I still don't tap but 10% of its power, despite using it daily, precisely because the key combinations seem arcane to me.

1ark 7y ago

I'm curious, how do you remember key combinations in other IDEs? I learned Vim, it was tough, but I remember a handful of commands I use all the time. And used Vim mode when available in IDEs when available. Spent a few years with VS Code, but I could never remember certain keys to navigate between panels for example. But the F1 key is great though. For w/e reason, I tried Emacs with evil-mode. I don't have to remember that many new keys I think, but a few of course. 'which-key' and M-x enables me to search for all commands, and I can also see the key combinations if I need to learn it later. In VS Code I try the F1 key, but if I could not find it there, I would grab the mouse and click around in menus looking for key combinations. Or go into settings and try to find w/e I was looking for. Of course, in Emacs I have spent hours setting things up, searching on the internet for clues on how to get something working as expected. Perhaps I am doing something non-optimal in my process. Curious how others learn/get productive in their respective IDEs.

pwinnski 7y ago
In most IDEs, they're the same key combos I use in non-IDE products. I'm on a Mac, so Cmd-X, Cmd-C, and Cmd-V work pretty much everywhere. They even work at a terminal prompt, and the latter two work in vi. I did learn vi years ago, but I'm sure I still don't tap but 10% of its power, despite using it daily, precisely because the key combinations seem arcane to me.