<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Understanding the &#8220;improved&#8221; in VIM</title>
	<atom:link href="http://blog.superuser.com/2012/03/06/understanding-the-improved-in-vim/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.superuser.com/2012/03/06/understanding-the-improved-in-vim/</link>
	<description>The Super User Community Blog</description>
	<lastBuildDate>Thu, 23 May 2013 15:40:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Web softwares - Vim &#124; Pearltrees</title>
		<link>http://blog.superuser.com/2012/03/06/understanding-the-improved-in-vim/#comment-5955</link>
		<dc:creator>Web softwares - Vim &#124; Pearltrees</dc:creator>
		<pubDate>Sat, 10 Mar 2012 14:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.superuser.com/?p=4811#comment-5955</guid>
		<description><![CDATA[&lt;p&gt;[...] Sometimes, every once in a while, a programmer feels like I do. VIM should be more efficient, more effective for editing text files yet I find myself reverting to the modern mouse-based approach more often than not. A rather famous question on Stack Overflow asked for tips on how to be more productive with VIM – and he got one of the best answers I’ve ever seen. Not a list of tips but a working, detailed explanation from Stack Overflow user Jim Dennis . It’s so good, I am copying his answer’s raw source here, running it through the Markdown parser and copied it here. So, without further ado, over to Jim’ amazing answer.  Understanding the “improved” in VIM - Super User Blog [...]&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>[...] Sometimes, every once in a while, a programmer feels like I do. VIM should be more efficient, more effective for editing text files yet I find myself reverting to the modern mouse-based approach more often than not. A rather famous question on Stack Overflow asked for tips on how to be more productive with VIM – and he got one of the best answers I’ve ever seen. Not a list of tips but a working, detailed explanation from Stack Overflow user Jim Dennis . It’s so good, I am copying his answer’s raw source here, running it through the Markdown parser and copied it here. So, without further ado, over to Jim’ amazing answer.  Understanding the “improved” in VIM &#8211; Super User Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Rowe</title>
		<link>http://blog.superuser.com/2012/03/06/understanding-the-improved-in-vim/#comment-5890</link>
		<dc:creator>Steve Rowe</dc:creator>
		<pubDate>Fri, 09 Mar 2012 23:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.superuser.com/?p=4811#comment-5890</guid>
		<description><![CDATA[&lt;p&gt;The sad part is that this information is almost being deleted on StackOverflow.  It will soon be lost.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>The sad part is that this information is almost being deleted on StackOverflow.  It will soon be lost.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Bobson</title>
		<link>http://blog.superuser.com/2012/03/06/understanding-the-improved-in-vim/#comment-5880</link>
		<dc:creator>Bob Bobson</dc:creator>
		<pubDate>Fri, 09 Mar 2012 20:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.superuser.com/?p=4811#comment-5880</guid>
		<description><![CDATA[&lt;p&gt;Reminds me of Edlin.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Reminds me of Edlin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alois Mahdal</title>
		<link>http://blog.superuser.com/2012/03/06/understanding-the-improved-in-vim/#comment-5876</link>
		<dc:creator>Alois Mahdal</dc:creator>
		<pubDate>Fri, 09 Mar 2012 20:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.superuser.com/?p=4811#comment-5876</guid>
		<description><![CDATA[&lt;p&gt;It&#039;s nice to remind this wonderful post by Jim Dennis.&lt;/p&gt;

&lt;p&gt;But honestly: Maybe I&#039;m missing something, but I don&#039;t really understand the point of re-posting it on this blog.  We all live in SU, don&#039;t we?&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s nice to remind this wonderful post by Jim Dennis.</p>

<p>But honestly: Maybe I&#8217;m missing something, but I don&#8217;t really understand the point of re-posting it on this blog.  We all live in SU, don&#8217;t we?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay</title>
		<link>http://blog.superuser.com/2012/03/06/understanding-the-improved-in-vim/#comment-5648</link>
		<dc:creator>Jay</dc:creator>
		<pubDate>Wed, 07 Mar 2012 11:22:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.superuser.com/?p=4811#comment-5648</guid>
		<description><![CDATA[&lt;p&gt;one of the improvements i wish vim hadn&#039;t made was break the undo-redo sequence &#039;uu&#039;, making it instead of multiple undo.  nvi&#039;s solution of &#039;u.&#039; to do multiple undo would have been better.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>one of the improvements i wish vim hadn&#8217;t made was break the undo-redo sequence &#8216;uu&#8217;, making it instead of multiple undo.  nvi&#8217;s solution of &#8216;u.&#8217; to do multiple undo would have been better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blog.superuser.com/2012/03/06/understanding-the-improved-in-vim/feed/ ) in 0.28394 seconds, on May 25th, 2013 at 8:52 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on May 25th, 2013 at 8:57 am UTC -->