<?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: vi: Teaching an old tech new tricks</title>
	<atom:link href="http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=vi-teaching-an-old-tech-new-tricks</link>
	<description>Just a Big Ball of Gas</description>
	<lastBuildDate>Fri, 03 Jun 2011 04:41:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Software Development Guide</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-7221</link>
		<dc:creator>Software Development Guide</dc:creator>
		<pubDate>Sun, 11 Nov 2007 04:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-7221</guid>
		<description>&lt;strong&gt;Software Development Guide...&lt;/strong&gt;

I couldn&#039;t understand some parts of this article, but it sounds interesting...</description>
		<content:encoded><![CDATA[<p><strong>Software Development Guide&#8230;</strong></p>
<p>I couldn&#8217;t understand some parts of this article, but it sounds interesting&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: randomwalker</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-3305</link>
		<dc:creator>randomwalker</dc:creator>
		<pubDate>Tue, 17 Jul 2007 06:39:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-3305</guid>
		<description>As for extra packages, you might needs ctags if you don&#039;t have it. Other than that I can&#039;t think of anything.

Look for some sample .vimrc&#039;s on the web if you have time. You&#039;ll find many definitions and macros that save a lot of time and trouble. You can reuse the ones that you think are useful to you instead of reinventing them.</description>
		<content:encoded><![CDATA[<p>As for extra packages, you might needs ctags if you don&#8217;t have it. Other than that I can&#8217;t think of anything.</p>
<p>Look for some sample .vimrc&#8217;s on the web if you have time. You&#8217;ll find many definitions and macros that save a lot of time and trouble. You can reuse the ones that you think are useful to you instead of reinventing them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-3302</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Tue, 17 Jul 2007 02:04:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-3302</guid>
		<description>Too many VI cheat sheets want you to memorize what appears to be random gibberish.

The truth is that there is a structure to the VI command set.  I have linked my name (above) to the list of cheat sheets that I make available to my students (and the rest of the &#039;net, of course!).  Please forgive the rather hokey layout; I&#039;ll change that one of these days...  In the meantime, if you scroll down towards the bottom you&#039;ll find a link to the VI cheat sheet.  In summary, the cheat sheet shows that you can take &quot;one from column A and one from column B&quot; to create most VI commands.  There are a few exceptions and the common ones are right smack in the middle of the first page of the cheat sheet.

Hope that helps.</description>
		<content:encoded><![CDATA[<p>Too many VI cheat sheets want you to memorize what appears to be random gibberish.</p>
<p>The truth is that there is a structure to the VI command set.  I have linked my name (above) to the list of cheat sheets that I make available to my students (and the rest of the &#8216;net, of course!).  Please forgive the rather hokey layout; I&#8217;ll change that one of these days&#8230;  In the meantime, if you scroll down towards the bottom you&#8217;ll find a link to the VI cheat sheet.  In summary, the cheat sheet shows that you can take &#8220;one from column A and one from column B&#8221; to create most VI commands.  There are a few exceptions and the common ones are right smack in the middle of the first page of the cheat sheet.</p>
<p>Hope that helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heartsmagic</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-3298</link>
		<dc:creator>Heartsmagic</dc:creator>
		<pubDate>Mon, 16 Jul 2007 21:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-3298</guid>
		<description>Also check http://vim.wikia.com/wiki/Category:VimTip</description>
		<content:encoded><![CDATA[<p>Also check <a href="http://vim.wikia.com/wiki/Category:VimTip" rel="nofollow">http://vim.wikia.com/wiki/Category:VimTip</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marius Gedminas</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-3296</link>
		<dc:creator>Marius Gedminas</dc:creator>
		<pubDate>Mon, 16 Jul 2007 20:50:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-3296</guid>
		<description>I learned most of the cool things by reading the online :help, back when I still had lots of spare time.

Most useful advanced vim features for me are:

 - word completion (^P/^N in insert mode)
 - window splits (^W s, ^W v)
 - jumping to class/function definitions (^] after building a tags file with :!ctags -R .)
 - jumping to filename under cursor (gf)
 - interactive diffs (vimdiff file1 file2)

I also quite like the high-level editing commands (e.g. &quot;change the contents of the current HTML element to something else&quot; -&gt; citsomething else).</description>
		<content:encoded><![CDATA[<p>I learned most of the cool things by reading the online :help, back when I still had lots of spare time.</p>
<p>Most useful advanced vim features for me are:</p>
<p> &#8211; word completion (^P/^N in insert mode)<br />
 &#8211; window splits (^W s, ^W v)<br />
 &#8211; jumping to class/function definitions (^] after building a tags file with :!ctags -R .)<br />
 &#8211; jumping to filename under cursor (gf)<br />
 &#8211; interactive diffs (vimdiff file1 file2)</p>
<p>I also quite like the high-level editing commands (e.g. &#8220;change the contents of the current HTML element to something else&#8221; -&gt; citsomething else).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bastl</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-3295</link>
		<dc:creator>Bastl</dc:creator>
		<pubDate>Mon, 16 Jul 2007 20:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-3295</guid>
		<description>now...

Ive assembled  a reference card that maps ideas to cryptic commands, not the other way round as you&#039;ll find many more. Find mine here: http://simpletutorials.com/html/vim/vimquick.pdf. If you fill out a lot of web forms, try out the &quot;It&#039;s all text&quot; plugin for firefox. (also works for emacs, but i guess it&#039;s slower ;-) )

The link to the vim tips is here: http://vim.wikia.com
 
Two more tips: 
* learn the concepts of vim, not stupid commands like &quot;ZZ&quot; or &quot;wq&quot;. The &quot;modes&quot; and extensibility is what makes vim special. 
* Search for the &quot;7 habits of text editing&quot; of bram. quite useful, and mainly independent of the editor ...

I think thats all. Vim rocks!

Sebastian.</description>
		<content:encoded><![CDATA[<p>now&#8230;</p>
<p>Ive assembled  a reference card that maps ideas to cryptic commands, not the other way round as you&#8217;ll find many more. Find mine here: <a href="http://simpletutorials.com/html/vim/vimquick.pdf" rel="nofollow">http://simpletutorials.com/html/vim/vimquick.pdf</a>. If you fill out a lot of web forms, try out the &#8220;It&#8217;s all text&#8221; plugin for firefox. (also works for emacs, but i guess it&#8217;s slower <img src='http://www.mikesplanet.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  )</p>
<p>The link to the vim tips is here: <a href="http://vim.wikia.com" rel="nofollow">http://vim.wikia.com</a></p>
<p>Two more tips:<br />
* learn the concepts of vim, not stupid commands like &#8220;ZZ&#8221; or &#8220;wq&#8221;. The &#8220;modes&#8221; and extensibility is what makes vim special.<br />
* Search for the &#8220;7 habits of text editing&#8221; of bram. quite useful, and mainly independent of the editor &#8230;</p>
<p>I think thats all. Vim rocks!</p>
<p>Sebastian.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bastl</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-3294</link>
		<dc:creator>Bastl</dc:creator>
		<pubDate>Mon, 16 Jul 2007 20:34:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-3294</guid>
		<description>Checkout the vimtips: over 1500 Tips since 2/2001

Also search the archive of vim@vim.org on mail-archive.org. Subscribe to vim-experiment@googlegroups.com . There is a very friendly and helpful community even for newbies. vimtutor has been mentioned. Learn to use the :help. Take your time. You need at least a year to get comfortable with vim. Rumours say that you own the editor if you know what typing your name would do in vim. There are a lot of cool scripts that are not enabled by default search them in the vim runtime. shit batteries empty. ...</description>
		<content:encoded><![CDATA[<p>Checkout the vimtips: over 1500 Tips since 2/2001</p>
<p>Also search the archive of <a href="mailto:vim@vim.org">vim@vim.org</a> on mail-archive.org. Subscribe to <a href="mailto:vim-experiment@googlegroups.com">vim-experiment@googlegroups.com</a> . There is a very friendly and helpful community even for newbies. vimtutor has been mentioned. Learn to use the :help. Take your time. You need at least a year to get comfortable with vim. Rumours say that you own the editor if you know what typing your name would do in vim. There are a lot of cool scripts that are not enabled by default search them in the vim runtime. shit batteries empty. &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Kavanagh</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-3291</link>
		<dc:creator>Ryan Kavanagh</dc:creator>
		<pubDate>Mon, 16 Jul 2007 19:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-3291</guid>
		<description>The University of Hawaii has a nice cheet sheet at the bottom of it&#039;s tutor: http://www.eng.hawaii.edu/Tutor/vi.html</description>
		<content:encoded><![CDATA[<p>The University of Hawaii has a nice cheet sheet at the bottom of it&#8217;s tutor: <a href="http://www.eng.hawaii.edu/Tutor/vi.html" rel="nofollow">http://www.eng.hawaii.edu/Tutor/vi.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Clowers</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-3290</link>
		<dc:creator>Kelly Clowers</dc:creator>
		<pubDate>Mon, 16 Jul 2007 18:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-3290</guid>
		<description>My favorite tutorial:
&lt;a href=&quot;http://www.vi-improved.org/tutorial.php&quot; rel=&quot;nofollow&quot;&gt;http://www.vi-improved.org/tutorial.php&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>My favorite tutorial:<br />
<a href="http://www.vi-improved.org/tutorial.php" rel="nofollow">http://www.vi-improved.org/tutorial.php</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierce</title>
		<link>http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/comment-page-1/#comment-3287</link>
		<dc:creator>Pierce</dc:creator>
		<pubDate>Mon, 16 Jul 2007 18:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikesplanet.net/2007/07/vi-teaching-an-old-tech-new-tricks/#comment-3287</guid>
		<description>Personally, I&#039;m not a fan of gvim or cream. I would suggest &#039;apt-get install vim&#039; which installs everything, I want, syntax and coloring and all that, without gvim. Vim is all about the little commands you pick up over long periods of time, which make moving around and manipulating text more flexible (but it does take a long time to pick it all up and get used to it). As for my .vimrc: syntax on, set ruler autoindent smartindent</description>
		<content:encoded><![CDATA[<p>Personally, I&#8217;m not a fan of gvim or cream. I would suggest &#8216;apt-get install vim&#8217; which installs everything, I want, syntax and coloring and all that, without gvim. Vim is all about the little commands you pick up over long periods of time, which make moving around and manipulating text more flexible (but it does take a long time to pick it all up and get used to it). As for my .vimrc: syntax on, set ruler autoindent smartindent</p>
]]></content:encoded>
	</item>
</channel>
</rss>

