|
bollig posted:Long story short, I want to keep the VIM keybindings (at least for text editing/coding) but want to do the emacs poo poo. Why do you want to force emacs into vi keybindings? You'll get a subpar experience of both. Just use emacs as Steele and Moon decreed, and all shall be good.
|
#
¿
May 10, 2015 01:20
|
|
|
|
| # ¿ May 10, 2024 13:55 |
|
|
Flat Daddy posted:How will it be a subpar experience? Let's say you start using a new mode because you're learning a new language or something. Among other things it'll have its set of key bindings to learn. They'll probably build on existing emacs bindings. In cases where they're literally building on emacs bindings, they'll probably be adapted automatically to your vi-compatible bindings. In cases where they're only doing so figuratively though, you'll have this mismatch between how you're used to doing things and how the new thing expects you to work. If you stay in the emacs world, this won't happen.
|
|
#
¿
May 11, 2015 04:35
|
|
|
Love Stole the Day posted:I remember reading once that Jobs was an Emacs person, that's probably why SJ was a GUI person, the emacs functionality is there because NeXT folks were largely emacs people. Also back then vi wasn't fetishized the same way it is today, people used it because it was ubiquitous and small and fast, not because they thought modal editing was somehow more efficient for their use. Remember, eight megs and constantly swapping was a meaningful criticism of emacs once upon a time. eschaton fucked around with this message at 11:42 on Dec 12, 2016 |
|
#
¿
Dec 12, 2016 11:39
|
|
|
MALE SHOEGAZE posted:yeah it doesn't matter, every serious vim user rebinds escape, ctrl, etc, to better things. What serious vim users? Most vim users are just using it because some other techbro on HN said it was the way to really crush code when getting down to the metal with Node.js.
|
|
#
¿
Dec 12, 2016 17:54
|
|
|
Would that you could just use //nodename/path/to/file…
|
|
#
¿
Jan 20, 2017 20:22
|
|