What features am I missing when I use Vim instead of Emacs?
|
|
As a Vim (and probably a future Emacs) user I miss
but as an ex-Emacs user I don't miss
|
|||||||||||||||||||||
|
|
One thing that Emacs has that seems impossible to do in Vim is to detect changes in a file and act upon them. There is no "FileChanged" event to hook into. This means writing complex plugins such as org-mode is nigh-on impossible in Vim. You have to fudge it by tracking cursor movement, which adds lots of corner cases that cause slip ups. I wrote a plugin for Vim to emulate Emacs's diff-mode for editing patches and hit upon this issue. It works, but requires some inelegant This is probably also why there are far fewer plugins for Vim that integrate external tools in the same way that there are for Emacs. There is no clean way to map Alt/Meta and a keypress to an action in Vim. There are numerous workarounds, but none of them work particularly well in all cases. If you use a UTF-8 shell and terminal Vim, you are mostly out of luck. This means that you can't emulate the readline/Emacs keys in insert mode as is attempted in the Vimacs plugin. It may break in GVim or in terminal Vim depending on how you do it. One other difference is that in Emacs the key mappings are uniform in all of the edit buffers. Vim has a different set of keyboard shortcuts when you are in command mode after typing a :. These keys are not like the usual readline mappings, nor are they like the rest of the Vim keys. For example, you have to use Shift-Left to go back a word instead of typing b. Hitting Ctrl-F enters a strange edit buffer for the command line that has its own set of rules. This makes opening new files a bit of a pain as you have to remember that you are not on the command line, nor are you in regular Vim. I use Vim exclusively - including using It's All Text! - but I appreciate where Emacs is coming from. |
|||
|
|
Org-mode is an absolutely fabulous outliner, GTD/todo manager, note organizer and general framework for writing, which is developed as an Emacs major mode. It has a fantastic lead developer (Carsten Dominik, see his Google Tech Talk video), and a great community. I was a happy Vim user for 12 years, and still gladly do the odd config file inn in it. But mainly now I'm a very happy org-mode (therefore Emacs) user. No other open source outliner comes within leagues of it in function or flexibility. I do all my PhD writing and note-taking in it. |
|||
|
|
|
Emacs has a vi mode, but vi does not have (as far as I know) an emacs mode. EDIT: And don't forget C-x M-c M-butterfly |
|||||||||||||
|
|
|
|||||||||
|
|
Better completion and lisp instead of vimscript... Edit: There is also a really good comparison here: http://www.io.com/~dierdorf/emacsvi.html |
|||||||||
|
|
You actually have to leave your editor to use the operating system if you use Vim. I use emacs because of emacspeak and all the applications it works with like AIM, spreadsheets, etc. |
|||
|
|
|
Never used vim really for more than basic vi features (so correct me if I am wrong), but I don't think you can do with vim (except with external processes of course)
|
|||
|
How about phases of the moon? http://www.gnu.org/software/emacs//manual/html_node/emacs/Lunar-Phases.html |
|||
|
|
|
There are no foot pedals available vor vim. |
|||||
|
|
The big difference for me between vi(m) and emacs is the core UI experience of modality. In vi(m) you have the big split between edit mode, and command/navigation mode. In emacs, you pretty much start typing and use wild metacharacter sequences to get what you want. Both are kind of hard to get used to, but once you are used to it you've got so much pattern embedded in your brain (read:muscle memory) that it's hard to switch. (Though there is Cream that loosens the modality of vim a bit) The other big thing is the concept of extensibility. vi came about in the real real old days of UNIX, where a small terse editor was mandatory given memory constraints. Emacs came a bit later, when machines were slightly more generous with RAM, and the goal seemed to isolate from the command environment a bit more, and keep you in Emacs. As such, emacs has a rich history of scripts and ability to do things other than editing. The joke goes "Emacs would make a fine OS if someone would just write a decent text editor for it". As such, either is fine. Whichever editor you start to use, you'll get very used to the patterns of usage, and it will be harder for you to switch. As for me, I dislike the modality of vi, and the complexity of emacs, and I use nedit for simple edits, though it's very long in the tooth now. A simple config, and it tries to stay out of my way. If I don't have X, I'll use vi, and curse the modality and not having X. |
|||
|
|

