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

[{'answer_id': 14415, 'author': 'Rytmis', 'author_id': 266, 'author_profile': 'https://Stackoverflow.com/users/266', 'pm_score': 3, 'selected': False, 'text': "<p>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? :) </p>\n"}, {'answer_id': 14416, 'author': 'Peter Stuifzand', 'author_id': 1633, 'author_profile': 'https://Stackoverflow.com/users/1633', 'pm_score': 2, 'selected': False, 'text': '<p>I believe Eclipse has Vi bindings and there is a Visual Studio plugin/extension, too (which is called Vi-Emu, or something).</p>\n'}, {'answer_id': 14489, 'author': 'Leon Bambrick', 'author_id': 49, 'author_profile': 'https://Stackoverflow.com/users/49', 'pm_score': 7, 'selected': True, 'text': '<p>Early software was often modal, but usability took a turn at some point, away from this style. </p>\n\n<p>VI-based editors are total enigmas -- they\'re the only real surviving members of that order of software. </p>\n\n<p>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. </p>\n\n<p>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".</p>\n\n<p>To learn more, search for the term "modeless" (and "usability")</p>\n\n<p>As mentioned in the comments below, a Modal interface in the hands of an experienced and non-fickle person can be extremely efficient.</p>\n'}, {'answer_id': 14524, 'author': 'fulmicoton', 'author_id': 446497, 'author_profile': 'https://Stackoverflow.com/users/446497', 'pm_score': 1, 'selected': False, 'text': '<p>Though not really answering your question, there used to be a "modal like" way to write Japanese on cell phones before :\nThe 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)</p>\n\n<p>Though it was main a few years ago, today it\'s only used by people who really want to hit fast.</p>\n'}, {'answer_id': 15217, 'author': 'OJ.', 'author_id': 611, 'author_profile': 'https://Stackoverflow.com/users/611', 'pm_score': 3, 'selected': False, 'text': '<p>@Leon: Great answer.</p>\n\n<p>@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 ;)</p>\n'}, {'answer_id': 31124, 'author': 'Hamish Downer', 'author_id': 3189, 'author_profile': 'https://Stackoverflow.com/users/3189', 'pm_score': 1, 'selected': False, 'text': '<p>I recently came across <a href="http://www.cs.brown.edu/research/plt/software/divascheme/" rel="nofollow noreferrer">divascheme</a> - an alternative set of key bindings for <a href="http://www.drscheme.org/" rel="nofollow noreferrer">DrScheme</a>.  This is modal, and part of the justification is to do with RSI - specifically avoiding lots of wrist twisting to hit <kbd>Ctrl</kbd>-<kbd>Alt</kbd>-<kbd>Shift</kbd>-<kbd>something</kbd>.  The coder has done an informal survey of fellow coders and found that emacs users suffered from more wrist pain than vi coders.</p>\n\n<p>You can see him doing a <a href="http://video.google.com/videoplay?docid=-2721456512458968128&amp;hl=en" rel="nofollow noreferrer">short talk</a> at <a href="http://lugradio.org/live/USA2008/" rel="nofollow noreferrer">LugRadio Live USA</a>.  (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).</p>\n\n<p>Note I have not used divascheme.</p>\n'}, {'answer_id': 371640, 'author': 'Paul Tomblin', 'author_id': 3333, 'author_profile': 'https://Stackoverflow.com/users/3333', 'pm_score': 3, 'selected': False, 'text': "<p>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.</p>\n"}, {'answer_id': 373112, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 2, 'selected': False, 'text': "<p>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.</p>\n\n<p>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. </p>\n"}, {'answer_id': 537684, 'author': 'Rafał Dowgird', 'author_id': 12166, 'author_profile': 'https://Stackoverflow.com/users/12166', 'pm_score': 3, 'selected': False, 'text': "<p>I think that it's because vi (and its ilk) already occupies the ecological niche of modal editors.</p>\n\n<p>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.</p>\n"}, {'answer_id': 2710138, 'author': 'Hamish Downer', 'author_id': 3189, 'author_profile': 'https://Stackoverflow.com/users/3189', 'pm_score': 1, 'selected': False, 'text': '<p>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 <em>they all use the vi key bindings</em>. 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.</p>\n\n<p>But lots of different editors have re-implemented the vi key bindings from scratch. Just look at <a href="https://stackoverflow.com/questions/294613/does-any-ide-have-a-vi-keybindings-options">this question about IDEs with vi key bindings</a>. At least half of the answers are editors built from scratch that implement vi key bindings, not versions of vi embedded.</p>\n'}, {'answer_id': 2971563, 'author': 'Andrew Wagner', 'author_id': 139802, 'author_profile': 'https://Stackoverflow.com/users/139802', 'pm_score': 2, 'selected': False, 'text': "<p>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.  </p>\n"}, {'answer_id': 18217628, 'author': 'Paul Sweatte', 'author_id': 1113772, 'author_profile': 'https://Stackoverflow.com/users/1113772', 'pm_score': 1, 'selected': False, 'text': '<p>The invention of the <a href="http://www.wired.com/science/discoveries/news/2009/01/dayintech_0126" rel="nofollow noreferrer">mouse</a> took one mode and moved it to an input device, and context menus took another mode and moved it to a button. Ironically, the advent of touch devices has had the reverse effect, producing <a href="https://www.experiencedynamics.com/blog/2007/06/multi-modal-design-gesture-touch-and-mobile-devicesnext-big-thing" rel="nofollow noreferrer">multi-modal</a> interfaces:</p>\n<ul>\n<li><p>aware multi-modal - touch and speech are aware of each other and intersect</p>\n</li>\n<li><p>unaware multi-modal - touch and speech are unaware of each other and conflict</p>\n</li>\n</ul>\n<blockquote>\n<p>The traditional WIMP interfaces have the basic premise that the information can flow in and out of the system through a single channel or an event stream. This event stream can be in the form of input (mouse, keyboard etc) where the user enters data to the system and expects feedback in the form of output (voice, vibration, visual, etc) when the system responds. But the channel maintains its singularity and can process information one source at a time. For example, in today’s interaction, the computer ignores typed information (through a keyboard) when a mouse button is depressed.</p>\n<p>This is very much different from a multimodal interaction where the system has multiple event streams and channels and can process information coming through various input modes acting in parallel, such as those described above. For example, in an IVR system a user can either type or speak to navigate through the menu.</p>\n</blockquote>\n<p><strong>References</strong></p>\n<ul>\n<li><p><a href="http://www.w3.org/WAI/UA/work/wiki/Keyboard_Interface_use_cases" rel="nofollow noreferrer">User Agent Accessibility Guidelines working group (UAWG): Keyboard Interface use cases</a></p>\n</li>\n<li><p><a href="http://www.w3.org/2009/02/emma-pressrelease.html.en" rel="nofollow noreferrer">W3C Multimodal Standard Brings Web to More People, More Ways</a></p>\n</li>\n<li><p><a href="http://www.w3.org/Voice/multimodal-rfp.html" rel="nofollow noreferrer">Next steps for W3C work on Multimodal Standards</a></p>\n</li>\n<li><p><a href="http://johnnyholland.org/2008/11/the-future-of-interaction-is-it-multimodal/" rel="nofollow noreferrer">The Future of Interaction is Multimodal</a></p>\n</li>\n<li><p><a href="http://research.microsoft.com/en-us/um/people/nath/docs/naturalinfovis_infovis2012.pdf" rel="nofollow noreferrer">Beyond Mouse and Keyboard: Expanding Design Considerations for Information Visualization Interactions - naturalinfovis_infovis2012.pdf</a></p>\n</li>\n<li><p><a href="https://www.w3.org/People/Bos/webapps.html" rel="nofollow noreferrer">Setting the scope for light-weight Web-based applications</a></p>\n</li>\n<li><p><a href="https://archive.wired.com/science/discoveries/news/2009/01/dayintech_0126" rel="nofollow noreferrer">Jan. 26, 1983: Spreadsheet as Easy as 1-2-3</a></p>\n</li>\n<li><p><a href="https://www.experiencedynamics.com/blog/2007/06/multi-modal-design-gesture-touch-and-mobile-devicesnext-big-thing" rel="nofollow noreferrer">Multi-modal design: Gesture, Touch and Mobile devices...next big thing? | Experience Dynamics</a></p>\n</li>\n</ul>\n'}, {'answer_id': 24575167, 'author': 'Ben C', 'author_id': 2319122, 'author_profile': 'https://Stackoverflow.com/users/2319122', 'pm_score': 2, 'selected': False, 'text': '<p>Remember that Notepad is a modal editor!</p>\n\n<p>To see this, try typing <kbd>E</kbd>, <kbd>D</kbd>, <kbd>I</kbd>, <kbd>T</kbd>; now try typing <kbd>Alt</kbd>, <kbd>E</kbd>, <kbd>D</kbd>, <kbd>I</kbd>, <kbd>T</kbd>.  In the second case the Alt key activates the "menu mode" so the results are different. :oP  People seem to cope with that.</p>\n\n<p>(Yes, this is a feature of Windows rather than specifically of Notepad.  I think it\'s a bad feature because it is easy to hit Alt by mistake and I don\'t think you can turn it off.)</p>\n'}, {'answer_id': 57312979, 'author': 'alife', 'author_id': 9317690, 'author_profile': 'https://Stackoverflow.com/users/9317690', 'pm_score': 2, 'selected': False, 'text': '<p><em>Since this is a question already at odds with the "no subjective issues" mantra, allow me to face that head on in kind.</em></p>\n\n<p>Non-Modal editing seeks to solve the problem caused by non-modal editing in the first place.</p>\n\n<p>Simply put, with Modal editing I can do nearly everything without my hands leaving the keyboard, and without even tormenting my pinky with reaching for the control, or interrupting my finger placement by hunting for the arrow keys.</p>\n\n<ol>\n<li><p>Reaching for mouse completely interrupts the train of thought.  I have hated the intense reliance upon this with Intellij IDEA and Netbeans for many years.  Even with vim-style addons.</p></li>\n<li><p>Most of what you do has to do with fine-tuning with very small increments and changes within the same paragraph of code.  Move up, move over, change character, etc., etc.  These things are interrupted with control keys and arrows and mouse.</p></li>\n</ol>\n'}]
['https://Stackoverflow.com/questions/14410', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/745/']