tags:

views:

1148

answers:

12

Pretty much every other editor that isn't a vi descendant (vim, cream, vi-emu) seems to use the emacs shortcuts (ctrl+w to delete back a word and so on)

+7  A: 

Um... maybe there isn't much of a need for one, given that Vi/Vim is pretty much available everywhere and got the whole modal thing right? :)

Rytmis
+2  A: 

I believe Eclipse has Vi bindings and there is a Visual Studio plugin/extension, too (which is called Vi-Emu, or something).

Peter Stuifzand
+3  A: 

@Peter: The Eclipse extension is called ViPlugin and the VS.Net extension is, like you said, ViEmu.

Rytmis
There is also open source Eclipse plugin called Vrapperhttp://vrapper.sourceforge.net/home/
Krzysiek Goj
+24  A: 

Early software was often modal, but usability took a turn at some point, away from this style.

VI-based editors are total enigmas -- they're the only real surviving members of that order of software.

Modes are a no-no in usability and interaction design because we humans are fickle mammals who cannot be trusted to remember what mode the application is in.

If you think you are in one "mode" when you are actually in another, then all sorts of badness can ensue. What you believe to be a series of harmless keystrokes can (in the wrong mode) cause unlimited catastrophe. This is known as a "mode error".

To learn more, search for the term "modeless" (and "usability")

Leon Bambrick
While your answer does a good job of discussing the bad parts of modal interfaces for new users, it does not address the significant efficiency gains that a modal interface offers to experienced users. Perhaps you could edit your answer to address the benefits as well?
Hudson
+1 for "fickle mammals" -- makes UI design an interesting experience :)
bedwyr
Sometimes the most obvious interface for a beginner is not the best... Some really good things take a little investment!
Tony Lambert
Sometimes the purported "productivity gains" from the "investment" are an excuse made after the fact to excuse the time wasted on the investment. I know and use vi/m. I know and use several other editors (but not EMACS). I've never seen a noticeable increase in productivity from any of them no matter how much time or effort I "invest" in them, largely because when I'm doing software right typing text is not my major activity. Thinking is.
JUST MY correct OPINION
A: 

Though not really answering your question, there used to be a "modal like" way to write Japanese on cell phones before : The first letter you hit was a conson let's say K, and then, and then the next key you would hit would have the role of a conson. (Having two conson in a row is impossible in Japanese)

Though it was main a few years ago, today it's only used by people who really want to hit fast.

poulejapon
+2  A: 

@Leon: Great answer.

@dbr: Modal editing is something that takes a while to get used to. If you were to build a new editor that fits this paradigm, how would you improve on VI/VIM/Emacs? I think that is, in part, an answer to the question. Getting it "right" is hard enough, competing agains the likes of VI/VIM/Emacs would be extremely tough -- most people who use these editors are "die hard" fans, and you'd have to give them a compelling reason to move to another editor. Those people who don't use them already are most likely going to stay in a non-modal editor. IMHO of course ;)

OJ
The way to get new users would be to do one aimed at a particular niche, such as divascheme I mention in my answer. Make it simple.That said I'm very happy with vim.
Hamish Downer
+1  A: 

I recently came across divascheme - an alternative set of key bindings for DrScheme. This is modal, and part of the justification is to do with RSI - specifically avoiding lots of wrist twisting to hit Ctrl-Alt-Shift-something. The coder has done an informal survey of fellow coders and found that emacs users suffered from more wrist pain than vi coders.

You can see him doing a short talk at LugRadio Live USA. (The video is a series of 5 minute talks and I can't remember how far through it is, sorry - if someone watches it and posts that here I'll edit this post to say when in the video it is).

Note I have not used divascheme.

Hamish Downer
+5  A: 

Modal editors have the huge advantage to touch typists that you can navigate around the screen without taking your hands off the home row. My wrists only hurt when I'm doing stuff that requires me to move my hand off the keyboard and onto the mouse or arrow keys and back constantly.

Paul Tomblin
+1  A: 

It's worth noting that the vi input models survival is in part due it's adoption in the POSIX standard, so investing time in learning would mean your guarenteed to be able to work on any system complying to these standards. So, like English, theres power in ubiquity.

As far as alternatives go, I doubt an alternate model editor would survive a 30 day free trial period, so its the same reason more people drive automatics than fly jets.

Europeans drive standards.
intuited
+1. The only reason I learned vi was because it was guaranteed to be on any Unix-alike. Other editors, not so much.
JUST MY correct OPINION
+2  A: 

I think that it's because vi (and its ilk) already occupies the ecological niche of modal editors.

The number of people who prefer modal and haven't yet been attracted to vi is probably 0, so the hypothetical vi competitor would have to be so great as to make a significant number of vi users switch. This isn't likely. The cost of switching editors is huge and the vi-s are probably already as good as modal editors go. Well, maybe a significant breakthrough could improve upon them, but I find this unlikely.

Rafał Dowgird
Very true, especially since you can overwrite any part of the default keybindings you don't like in your .vimrc.
Xiong Chiamiov
I think a significant breakthrough will be inevitable in a world filled with multi-touch devices. The ability to display contextual hints directly on the keys lowers the learning curve of modal interfaces significantly.
Drew Wagner
+2  A: 

I think the answer to the question is actually there are quite a few modal text editors that aren't forks of vi/vim. However they all use the vi key bindings. Vi users get the key bindings into their muscle memory so relearning a different set of key bindings would be really hard, so no-one would create a different set of key bindings.

But lots of different editors have re-implemented the vi key bindings from scratch. Just look at this question about IDEs with vi key bindings. At least half of the answers are editors built from scratch that implement vi key bindings, not versions of vi embedded.

Hamish Downer
Mmhmm. You'll notice that even things that aren't editors sometimes have vi-like keybindings (Gmail and Google Reader come to mind).
Xiong Chiamiov
+1  A: 

VIM and emacs make about as much user interface design sense as qwerty. We now have available modern computer optimized key layouts (see the colemak layout and the carpalx project); it's only a matter of time before someone does the same for text editors.

Drew Wagner
To clarify, I love vim's command set. The power of the commands alone results in a huge reduction in the number of button presses, but I feel like the key layout was driven more by mnemonics and backwards compatibility than by ergonomics. Perhaps this is just information theory at work though; the more efficient the commands get, the more randomly located they are.
Drew Wagner