<?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"
	>
<channel>
	<title>Comments on: vim: vi *improved*? my ass.</title>
	<atom:link href="http://kevinmcgowan.info/blog/2007/10/06/vim-vi-improved-my-ass/feed/" rel="self" type="application/rss+xml" />
	<link>http://kevinmcgowan.info/blog/2007/10/06/vim-vi-improved-my-ass/</link>
	<description>yet another linguistics blog.</description>
	<pubDate>Fri, 21 Nov 2008 10:22:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: willie</title>
		<link>http://kevinmcgowan.info/blog/2007/10/06/vim-vi-improved-my-ass/#comment-7</link>
		<dc:creator>willie</dc:creator>
		<pubDate>Tue, 09 Oct 2007 02:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://kevinmcgowan.info/blog/2007/10/06/vim-vi-improved-my-ass/#comment-7</guid>
		<description>Back in my day, whenever we'd make mistake, we were forced to live with it, and we liked it.  :)

BTW, try using the cntrl-R key combo to redo. cntrl-U is always undo, and cntrl-R is always redo. Just like opt-x, opt-c, and opt-v are always cut, copy and paste, they don't change depending on your context.

There are numerous features which make the traditional vi barely useful for development. It's lacking:

* multiple undos (or is it undoes?) If you change modes, then you lose access to all of your previous changes
* visual mode
* syntax coloring - saved me countless debugging hours
* long line support - try editing a large mysql data dump, vi will corrupt your file
* ex history - try doing a complex search &#38; replace on multiple files. When you go to your next file, you have to enter your expression again.

I've taken to making the old version of vi on my systems into a symlink to vim in order to save disk space.</description>
		<content:encoded><![CDATA[<p>Back in my day, whenever we&#8217;d make mistake, we were forced to live with it, and we liked it.  :)</p>
<p>BTW, try using the cntrl-R key combo to redo. cntrl-U is always undo, and cntrl-R is always redo. Just like opt-x, opt-c, and opt-v are always cut, copy and paste, they don&#8217;t change depending on your context.</p>
<p>There are numerous features which make the traditional vi barely useful for development. It&#8217;s lacking:</p>
<p>* multiple undos (or is it undoes?) If you change modes, then you lose access to all of your previous changes<br />
* visual mode<br />
* syntax coloring - saved me countless debugging hours<br />
* long line support - try editing a large mysql data dump, vi will corrupt your file<br />
* ex history - try doing a complex search &amp; replace on multiple files. When you go to your next file, you have to enter your expression again.</p>
<p>I&#8217;ve taken to making the old version of vi on my systems into a symlink to vim in order to save disk space.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
