<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Magic Syntax Enable in VIM</title>
	<link>http://tottinge.blogsome.com/2007/04/17/magic-syntax-enable-in-vim/</link>
	<description>Tim Ottinger on Christianity, freedom, software, podcasts, and really hot-looking guitars.</description>
	<pubDate>Fri, 16 May 2008 03:23:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Rhys</title>
		<link>http://tottinge.blogsome.com/2007/04/17/magic-syntax-enable-in-vim/#comment-588</link>
		<pubDate>Fri, 21 Sep 2007 13:32:21 +0100</pubDate>
		<guid>http://tottinge.blogsome.com/2007/04/17/magic-syntax-enable-in-vim/#comment-588</guid>
					<description>Hi,
I have a feeling that syntax enable also set the option 'nocompatible' and this is why everything started to work. Actually, it seems that as soon as a vimrc exists, nocompatible is turned on.

&lt;i&gt;Tim Says
&lt;blockquote&gt;
Yes.  I probably missed that detail.  I actaully was giddy when I realized that the 'syntax enable' had to be in the .vimrc file, and didn't work from the ':' command-line mode in the same way.  I thought I'd solved the whole thing.  I'll play with this and see how it turns out.
&lt;/blockquote&gt;
&lt;/i&gt;</description>
		<content:encoded><![CDATA[	<p>Hi,<br />
I have a feeling that syntax enable also set the option &#8216;nocompatible&#8217; and this is why everything started to work. Actually, it seems that as soon as a vimrc exists, nocompatible is turned on.</p>
	<p><i>Tim Says</p>
	<blockquote><p>
Yes.  I probably missed that detail.  I actaully was giddy when I realized that the &#8217;syntax enable&#8217; had to be in the .vimrc file, and didn&#8217;t work from the &#8216;:&#8217; command-line mode in the same way.  I thought I&#8217;d solved the whole thing.  I&#8217;ll play with this and see how it turns out.
</p></blockquote>
	<p></i>
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
