Comments on: The vi input model http://blog.ngedit.com/2005/06/03/the-vi-input-model/ A blog on the development of the NGEDIT text editor Sat, 04 Feb 2012 07:35:40 +0000 http://wordpress.org/?v=2.3.2 By: Eric Tetz http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-332362 Eric Tetz Fri, 20 May 2011 22:04:04 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-332362 Another thing worth mentioning is that Vim is ideal for telnet sessions or certain terminals where extended keys may not work as expected. Another thing worth mentioning is that Vim is ideal for telnet sessions or certain terminals where extended keys may not work as expected.

]]> By: Jon http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-277789 Jon Sun, 04 Oct 2009 10:17:32 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-277789 Artagnon, as the saying goes, Emacs is a great OS... it just lacks a decent editor! Artagnon, as the saying goes, Emacs is a great OS… it just lacks a decent editor!

]]> By: Artagnon http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-277788 Artagnon Sun, 04 Oct 2009 09:49:51 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-277788 I've been a faithful ViM for over four years. My muscle memory had progressed to the level where I couldn't even say which keys I was typing to do what- it just came to me naturally, much like touch typing. Felt absolutely awesome to be able to chain complex commands together unconciously and quickly build keyboard macros to repeat them. It's an absolutely awesome text editor, and there's no doubt about it. Early this year, as I became more of a programmer, I realized that I need a lot more than just plain text editing. It was extremely painful, but I finally switched to Emacs. It's possible that you'll discover Emacs someday too; and it's better that you do it earlier than later, especially if you're a very heavy programmer. ViM is undoubtedly a fantastic dumb-text editor, no doubt, but I encourage you to look at the other side just to get a glimpse of what you're missing. I’ve been a faithful ViM for over four years. My muscle memory had progressed to the level where I couldn’t even say which keys I was typing to do what- it just came to me naturally, much like touch typing. Felt absolutely awesome to be able to chain complex commands together unconciously and quickly build keyboard macros to repeat them. It’s an absolutely awesome text editor, and there’s no doubt about it.

Early this year, as I became more of a programmer, I realized that I need a lot more than just plain text editing. It was extremely painful, but I finally switched to Emacs. It’s possible that you’ll discover Emacs someday too; and it’s better that you do it earlier than later, especially if you’re a very heavy programmer. ViM is undoubtedly a fantastic dumb-text editor, no doubt, but I encourage you to look at the other side just to get a glimpse of what you’re missing.

]]> By: HURP DURP http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-250197 HURP DURP Wed, 25 Mar 2009 04:11:09 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-250197 Just kill yourself Just kill yourself

]]> By: J http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-228049 J Tue, 14 Oct 2008 10:45:16 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-228049 Sllik, I know about vimperator, but I'm not really much into it. I'm fine with a mouse for web browsing, it's only when editing that I miss vi/vim if I don't have them. I do know a few people who swear by vimperator though! I guess there will be many extensions for Chrome in time, but they should definitely build a common platform for Firefox/Chrome add-ons if they don't just want to dillute the efforts. Thanks for your feedback! - Jon Sllik, I know about vimperator, but I’m not really much into it. I’m fine with a mouse for web browsing, it’s only when editing that I miss vi/vim if I don’t have them. I do know a few people who swear by vimperator though!

I guess there will be many extensions for Chrome in time, but they should definitely build a common platform for Firefox/Chrome add-ons if they don’t just want to dillute the efforts.

Thanks for your feedback!

- Jon

]]> By: sLLiK http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-227323 sLLiK Fri, 10 Oct 2008 23:54:19 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-227323 There is a full-fledged Firefox makeover addon that turns your browser into a glorified vim. It's called vimperator, and it allows you to browse with hjkl, use : and other vi-centric methods to browse, open and browse bookmarks, open and close tabs, and just about everything you could think of. I haven't checked yet, but I don't think there's a polished version ready for Firefox 3.0 yet. I'm hoping Google Chrome will have something like that baked in. If it does, then I will likely switch to it. I'm thinking not anytime soon though, as Alt-# doesn't work for tab navigation... yet. There is a full-fledged Firefox makeover addon that turns your browser into a glorified vim. It’s called vimperator, and it allows you to browse with hjkl, use : and other vi-centric methods to browse, open and browse bookmarks, open and close tabs, and just about everything you could think of. I haven’t checked yet, but I don’t think there’s a polished version ready for Firefox 3.0 yet.

I’m hoping Google Chrome will have something like that baked in. If it does, then I will likely switch to it. I’m thinking not anytime soon though, as Alt-# doesn’t work for tab navigation… yet.

]]> By: Patrik http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-114398 Patrik Mon, 28 Jan 2008 20:10:36 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-114398 Thanks J, for the reply. I am hanging in the balance a bit, on whether to commit to vim or not. On the one hand, the underlying concepts appeal strongly to me - if nothing else, for it's sheer elegance. On the other hand, I will not be able to use it exclusivly or even for the most part, and I worry about only learning it half-assed. I do code sometimes, but maybe not often enough to keep me fluent in vi-commands. But you're saying that it's possible to treat is a normal editor at first, without being hampered. That's going on the pro list. It's a bit of a shame that the insert mode commands tend to be left out in the tutorials. They would really be helpful in giving you a "way in" to vi. There is also an issue with using other keyboards than standard english. Ctrl-] e.g. is quite difficult on a scandinavian keyboard - Ctrl-AltGr-9. Remapping isn't straightforward either in this case, since the target key is a dead key - it isn't even visible to the program until you press the next key. Same goes for backticks. Thanks J, for the reply.

I am hanging in the balance a bit, on whether to commit to vim or not. On the one hand, the underlying concepts appeal strongly to me - if nothing else, for it’s sheer elegance. On the other hand, I will not be able to use it exclusivly or even for the most part, and I worry about only learning it half-assed. I do code sometimes, but maybe not often enough to keep me fluent in vi-commands.

But you’re saying that it’s possible to treat is a normal editor at first, without being hampered. That’s going on the pro list.

It’s a bit of a shame that the insert mode commands tend to be left out in the tutorials. They would really be helpful in giving you a “way in” to vi.

There is also an issue with using other keyboards than standard english. Ctrl-] e.g. is quite difficult on a scandinavian keyboard - Ctrl-AltGr-9. Remapping isn’t straightforward either in this case, since the target key is a dead key - it isn’t even visible to the program until you press the next key. Same goes for backticks.

]]> By: J http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-114336 J Mon, 28 Jan 2008 13:30:01 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-114336 Hi Patrick, you're right. The case for vi/vim is less strong for regular 'prose' than it is for code or configuration files, etc... When writing, for example, an email, you stay much longer in insert mode. Once you're accustomed to it, though, you miss being able to press ESC and start moving around with compact commands. One way I like to see vi/vim editing is 'ESC on steroids': it's like a regular editor, but ESC opens a world of compact & very powerful commands. Since it's unobstrusive, you definitely miss it at least some times if you're used to it. So, yes, it's possible to use & useful for text entering, although if that's the sole use you do the case is not as strong as for code or other regularly formatted content. Hi Patrick, you’re right. The case for vi/vim is less strong for regular ‘prose’ than it is for code or configuration files, etc… When writing, for example, an email, you stay much longer in insert mode. Once you’re accustomed to it, though, you miss being able to press ESC and start moving around with compact commands.

One way I like to see vi/vim editing is ‘ESC on steroids’: it’s like a regular editor, but ESC opens a world of compact & very powerful commands. Since it’s unobstrusive, you definitely miss it at least some times if you’re used to it.

So, yes, it’s possible to use & useful for text entering, although if that’s the sole use you do the case is not as strong as for code or other regularly formatted content.

]]> By: Patrik http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-114118 Patrik Sun, 27 Jan 2008 21:42:59 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-114118 May I ask? The starting point always seems to be that you have a file, and would like to rearrange parts of it, injecting some small snippet of text here and there. How suitable is vi(m) for entering text in the first place, making corrections and reformatting as you're going. My guess has been that vim is not the right tool in these cases (since, conceptually, you would normally be in insert mode). But now I see people requesting it for, e.g., e-mail - where you would spend more time entering text than editing it. So, is it possible to use, and get used to, vim as text-entering tool? May I ask? The starting point always seems to be that you have a file, and would like to rearrange parts of it, injecting some small snippet of text here and there.
How suitable is vi(m) for entering text in the first place, making corrections and reformatting as you’re going. My guess has been that vim is not the right tool in these cases (since, conceptually, you would normally be in insert mode). But now I see people requesting it for, e.g., e-mail - where you would spend more time entering text than editing it.

So, is it possible to use, and get used to, vim as text-entering tool?

]]> By: J http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-100984 J Mon, 10 Dec 2007 12:07:49 +0000 http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-100984 Thanks Nat. I do most of my work in Windows, so the window manager stuff is not useful to me, but I've been and remain interested in trying out better window management systems. Windows is not too rich on those, so I'll give Linux a try at some time in the future (when I have more spare time!). Thanks Nat. I do most of my work in Windows, so the window manager stuff is not useful to me, but I’ve been and remain interested in trying out better window management systems. Windows is not too rich on those, so I’ll give Linux a try at some time in the future (when I have more spare time!).

]]>