<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for The growing pains of NGEDIT</title>
	<link>http://blog.ngedit.com</link>
	<description>A blog on the development of the NGEDIT text editor</description>
	<pubDate>Sat, 04 Feb 2012 07:22:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>Comment on Why, oh WHY, do those nutheads use vi? by Jason Kenney</title>
		<link>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-337029</link>
		<dc:creator>Jason Kenney</dc:creator>
		<pubDate>Tue, 02 Aug 2011 19:20:55 +0000</pubDate>
		<guid>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-337029</guid>
		<description>I use vi on osx with terminal full screen is an excellent distraction free environment.</description>
		<content:encoded><![CDATA[<p>I use vi on osx with terminal full screen is an excellent distraction free environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why, oh WHY, do those nutheads use vi? by Jon</title>
		<link>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-337001</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Tue, 02 Aug 2011 06:36:23 +0000</pubDate>
		<guid>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-337001</guid>
		<description>Steve, thanks for the comment. I think there is something like what you mention: the 'vimtutor'. In Unix, you just need to run 'vimtutor'. In Windows, you can look for vimtutor.bat in vim's installation directory. Start it, and you'll see that it's self-explaining and quite close to what you describe!</description>
		<content:encoded><![CDATA[<p>Steve, thanks for the comment. I think there is something like what you mention: the &#8216;vimtutor&#8217;. In Unix, you just need to run &#8216;vimtutor&#8217;. In Windows, you can look for vimtutor.bat in vim&#8217;s installation directory. Start it, and you&#8217;ll see that it&#8217;s self-explaining and quite close to what you describe!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why, oh WHY, do those nutheads use vi? by Steve Lehar</title>
		<link>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-336826</link>
		<dc:creator>Steve Lehar</dc:creator>
		<pubDate>Fri, 29 Jul 2011 15:12:10 +0000</pubDate>
		<guid>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-336826</guid>
		<description>Great article! I'm an old emacs guy (57 years old!) and just re-converting back to vi just to keep my mind fresh. One thing that would be VERY useful would be a plain-text file containing example code and explanatory text, so as you read the explanation you practice it immediately right on that text file, instead of having to pop over to another window to try what you've just learned. Example:

Try navigating through this text using w and b commands. Now put your cursor on () to the matching parenthesis. Now move your cursor {into these curly braces} and type da}. See what happens? Now type u to undo, and try dab and the same thing happens. But dab will also work within [square brackets] or {curly braces}, where you could also use da] and da} respectively.</description>
		<content:encoded><![CDATA[<p>Great article! I&#8217;m an old emacs guy (57 years old!) and just re-converting back to vi just to keep my mind fresh. One thing that would be VERY useful would be a plain-text file containing example code and explanatory text, so as you read the explanation you practice it immediately right on that text file, instead of having to pop over to another window to try what you&#8217;ve just learned. Example:</p>
<p>Try navigating through this text using w and b commands. Now put your cursor on () to the matching parenthesis. Now move your cursor {into these curly braces} and type da}. See what happens? Now type u to undo, and try dab and the same thing happens. But dab will also work within [square brackets] or {curly braces}, where you could also use da] and da} respectively.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The vi input model by Eric Tetz</title>
		<link>http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-332362</link>
		<dc:creator>Eric Tetz</dc:creator>
		<pubDate>Fri, 20 May 2011 22:04:04 +0000</pubDate>
		<guid>http://blog.ngedit.com/2005/06/03/the-vi-input-model/#comment-332362</guid>
		<description>Another thing worth mentioning is that Vim is ideal for telnet sessions or certain terminals where extended keys may not work as expected.</description>
		<content:encoded><![CDATA[<p>Another thing worth mentioning is that Vim is ideal for telnet sessions or certain terminals where extended keys may not work as expected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why, oh WHY, do those nutheads use vi? by Jim</title>
		<link>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-327129</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Tue, 22 Feb 2011 19:07:30 +0000</pubDate>
		<guid>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-327129</guid>
		<description>It's hard to go back to an IDE, I agree.  The trick to using VIM well is to find a tutorial that shows only 10-30 basic tricks.  Ignore those that try to show the full power of VIM in 1 blog post, you'll just feel overwhelmed.  I tried to use an IDE a few weeks ago, but with all the "helpful" popus and pauses, it would just ruin my concentration and productivity, never letting me get in the "zone" where I'm extremely productive, for more than 2 minutes.  VIM just gets out of the way, fades into the background, and does not ruin those important times of high productivity.</description>
		<content:encoded><![CDATA[<p>It&#8217;s hard to go back to an IDE, I agree.  The trick to using VIM well is to find a tutorial that shows only 10-30 basic tricks.  Ignore those that try to show the full power of VIM in 1 blog post, you&#8217;ll just feel overwhelmed.  I tried to use an IDE a few weeks ago, but with all the &#8220;helpful&#8221; popus and pauses, it would just ruin my concentration and productivity, never letting me get in the &#8220;zone&#8221; where I&#8217;m extremely productive, for more than 2 minutes.  VIM just gets out of the way, fades into the background, and does not ruin those important times of high productivity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why, oh WHY, do those nutheads use vi? by mandeep</title>
		<link>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-327109</link>
		<dc:creator>mandeep</dc:creator>
		<pubDate>Tue, 22 Feb 2011 14:31:15 +0000</pubDate>
		<guid>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-327109</guid>
		<description>the only drawback of learning vim that i faced was that i got so used to it's commands i was missing them everywhere, be it browser or excel document or word file ;-)</description>
		<content:encoded><![CDATA[<p>the only drawback of learning vim that i faced was that i got so used to it&#8217;s commands i was missing them everywhere, be it browser or excel document or word file <img src='http://blog.ngedit.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why, oh WHY, do those nutheads use vi? by 249</title>
		<link>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-318266</link>
		<dc:creator>249</dc:creator>
		<pubDate>Fri, 03 Dec 2010 05:19:29 +0000</pubDate>
		<guid>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-318266</guid>
		<description>Last year I decided (after getting sick of having to crack software to use it on windows) that I would go 100% Linux (Fedora to exact) and leave the worries of windows behind. I looked at and tried almost every editor that was/is available.. VI was/is the only editor for me. It was weird at first but, a few days of using it and I am hooked.</description>
		<content:encoded><![CDATA[<p>Last year I decided (after getting sick of having to crack software to use it on windows) that I would go 100% Linux (Fedora to exact) and leave the worries of windows behind. I looked at and tried almost every editor that was/is available.. VI was/is the only editor for me. It was weird at first but, a few days of using it and I am hooked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why, oh WHY, do those nutheads use vi? by Jon</title>
		<link>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-316399</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 15 Nov 2010 09:31:15 +0000</pubDate>
		<guid>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-316399</guid>
		<description>Regac, let me encourage you to climb the steep curve. It'll payoff later on!</description>
		<content:encoded><![CDATA[<p>Regac, let me encourage you to climb the steep curve. It&#8217;ll payoff later on!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why, oh WHY, do those nutheads use vi? by regac</title>
		<link>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-316213</link>
		<dc:creator>regac</dc:creator>
		<pubDate>Sat, 13 Nov 2010 19:57:39 +0000</pubDate>
		<guid>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-316213</guid>
		<description>Mind = blown. Accidentally stumbled upon this, and although I've tried Vim (and didn't like it) I just started to grasp its full potential.

I'll probably have to get around to learning it: too bad the learning curve is **steep**.</description>
		<content:encoded><![CDATA[<p>Mind = blown. Accidentally stumbled upon this, and although I&#8217;ve tried Vim (and didn&#8217;t like it) I just started to grasp its full potential.</p>
<p>I&#8217;ll probably have to get around to learning it: too bad the learning curve is **steep**.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why, oh WHY, do those nutheads use vi? by Jon</title>
		<link>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-314863</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 03 Nov 2010 18:06:02 +0000</pubDate>
		<guid>http://blog.ngedit.com/2007/05/17/why-oh-why-do-those-nutheads-use-vi/#comment-314863</guid>
		<description>Hey Rocman, actually, I can't express it any better than I did at the article above:

  http://www.viemu.com/a-why-vi-vim.html</description>
		<content:encoded><![CDATA[<p>Hey Rocman, actually, I can&#8217;t express it any better than I did at the article above:</p>
<p>  <a href="http://www.viemu.com/a-why-vi-vim.html" rel="nofollow">http://www.viemu.com/a-why-vi-vim.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

