4 ms·

yeah, definitely. Though, after having tried (and failed) to make the jump from vim => emacs a few times in the past, I can see that forcing yourself to use no

yeah, definitely. Though, after having tried (and failed) to make the jump from vim => emacs a few times in the past, I can see that forcing yourself to use nothing but emacs for 30 days would probably get yourself enough of a grounding to make the transition stick. If the whole emacs/lisp integration didn't look so much nicer (than vim/lisp) I would have given up trying to learn emacs a long time okay. One day though . . . I'm sure both of these will start to make sense =)

jerrya 16y ago
Emacs in 7 days: Day 1. Find a VT100, attach it to a dec10 or vax. Learn teco$$ Day 3. Move up to vmacs. Day 4. Move vax 1500 miles. Find 9600 baud modem and dial in. Day 5. Install unix. Learn qed or ed to get a real taste of the usefulness of regular expressions in moving around a line editor Day 6. emacs -nw. Luxurious, isn't it! Read the emacs lisp user guide. Day 7. learn about m-. Optional Day 8: Laugh at the eclipse losers.
- kragen 16y ago
  > Learn teco$$ This is pronounced "learn teco altmode altmode".
noahl 16y ago
Why not start with Viper? (Emacs' vi emulation.) I'm an Emacs user, but I've always been curious about trying that. It seems to me the big advantage of Emacs is its customizability, not its particular default keybindings. Maybe the vim ones are better. Viper could get you the best of both worlds.
- kemiller 16y ago
  Speaking as a Vi(m) user, viper is a pale imitation of the vi model. It gives you the basic keybindings all right, but you can tell its fake. Getting vi right is about more than keybindings. Undo doesn't behave predictably. You can't always compose commands the way you would in vi. Actions that would be a single discrete unit in vi become an awkward workaround. I wanted to like viper, because I like emacs's programming environment better than Vim's, but it's not worth sacrificing the feel and functionality of vim's editing model.
  - Xurinos 16y ago
    As a regular vim user, I recommend vimpulse if you want vim-like keybindings in emacs. IIRC, it even introduces some ":" functionality. It is still a pale imitation, but it is better than wrestling with default emacs keybindings in typical editing.

jerrya 16y ago

Emacs in 7 days: Day 1. Find a VT100, attach it to a dec10 or vax. Learn teco$$ Day 3. Move up to vmacs. Day 4. Move vax 1500 miles. Find 9600 baud modem and dial in. Day 5. Install unix. Learn qed or ed to get a real taste of the usefulness of regular expressions in moving around a line editor Day 6. emacs -nw. Luxurious, isn't it! Read the emacs lisp user guide. Day 7. learn about m-. Optional Day 8: Laugh at the eclipse losers.

kragen 16y ago
> Learn teco$$ This is pronounced "learn teco altmode altmode".

noahl 16y ago

Why not start with Viper? (Emacs' vi emulation.) I'm an Emacs user, but I've always been curious about trying that. It seems to me the big advantage of Emacs is its customizability, not its particular default keybindings. Maybe the vim ones are better. Viper could get you the best of both worlds.

kemiller 16y ago
Speaking as a Vi(m) user, viper is a pale imitation of the vi model. It gives you the basic keybindings all right, but you can tell its fake. Getting vi right is about more than keybindings. Undo doesn't behave predictably. You can't always compose commands the way you would in vi. Actions that would be a single discrete unit in vi become an awkward workaround. I wanted to like viper, because I like emacs's programming environment better than Vim's, but it's not worth sacrificing the feel and functionality of vim's editing model.
- Xurinos 16y ago
  As a regular vim user, I recommend vimpulse if you want vim-like keybindings in emacs. IIRC, it even introduces some ":" functionality. It is still a pale imitation, but it is better than wrestling with default emacs keybindings in typical editing.