<?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: The vimrc File</title>
	<atom:link href="http://www.derekwyatt.org/vim/the-vimrc-file/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.derekwyatt.org</link>
	<description>Vim... and stuff</description>
	<lastBuildDate>Wed, 25 Jan 2012 21:22:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Phiri</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-31101</link>
		<dc:creator>Phiri</dc:creator>
		<pubDate>Mon, 07 Nov 2011 09:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-31101</guid>
		<description>Great introduction to ~/.vimrc --I found it useful. Thank you for taking the time to write this. It would have been quite useful if you had included reference to place where those getting started could obtain more information.</description>
		<content:encoded><![CDATA[<p>Great introduction to ~/.vimrc &#8211;I found it useful. Thank you for taking the time to write this. It would have been quite useful if you had included reference to place where those getting started could obtain more information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fergal</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-26333</link>
		<dc:creator>fergal</dc:creator>
		<pubDate>Thu, 01 Sep 2011 17:39:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-26333</guid>
		<description>when i first started using vim on windows, it took me a while to find where i should be saving my .vimrc, until i realised i could just do 

:echo $HOME

to display my home directory, or

:e $HOME/.vimrc

to edit my vimrc directly. works on unix too!</description>
		<content:encoded><![CDATA[<p>when i first started using vim on windows, it took me a while to find where i should be saving my .vimrc, until i realised i could just do </p>
<p>:echo $HOME</p>
<p>to display my home directory, or</p>
<p>:e $HOME/.vimrc</p>
<p>to edit my vimrc directly. works on unix too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcin</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-26073</link>
		<dc:creator>Marcin</dc:creator>
		<pubDate>Sat, 27 Aug 2011 23:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-26073</guid>
		<description>I got inspired :) and published my own vimrc file here:
http://atp-vim.sf.net/help.shtml</description>
		<content:encoded><![CDATA[<p>I got inspired :) and published my own vimrc file here:<br />
<a href="http://atp-vim.sf.net/help.shtml" rel="nofollow">http://atp-vim.sf.net/help.shtml</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shrsv</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-18690</link>
		<dc:creator>shrsv</dc:creator>
		<pubDate>Wed, 25 May 2011 09:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-18690</guid>
		<description>I&#039;ve created a vimrc file generator.
Try it online here: http://vimrcgen.sourceforge.net/
In case you want an offline version: http://sourceforge.net/p/vimrcgen/home/</description>
		<content:encoded><![CDATA[<p>I&#8217;ve created a vimrc file generator.<br />
Try it online here: <a href="http://vimrcgen.sourceforge.net/" rel="nofollow">http://vimrcgen.sourceforge.net/</a><br />
In case you want an offline version: <a href="http://sourceforge.net/p/vimrcgen/home/" rel="nofollow">http://sourceforge.net/p/vimrcgen/home/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-13418</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Thu, 17 Mar 2011 05:58:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-13418</guid>
		<description>That pathogen sure makes it a lot easier. Thanks for your time man.</description>
		<content:encoded><![CDATA[<p>That pathogen sure makes it a lot easier. Thanks for your time man.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Wyatt</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-13344</link>
		<dc:creator>Derek Wyatt</dc:creator>
		<pubDate>Wed, 16 Mar 2011 09:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-13344</guid>
		<description>Everything that you customize should go in ~/.vim.  Failing to do that will make sure you have a pain in the ass upgrading Vim.

I also recommend that you use &#039;pathogen&#039;.  Read up on it here: http://tammersaleh.com/posts/the-modern-vim-config-with-pathogen</description>
		<content:encoded><![CDATA[<p>Everything that you customize should go in ~/.vim.  Failing to do that will make sure you have a pain in the ass upgrading Vim.</p>
<p>I also recommend that you use &#8216;pathogen&#8217;.  Read up on it here: <a href="http://tammersaleh.com/posts/the-modern-vim-config-with-pathogen" rel="nofollow">http://tammersaleh.com/posts/the-modern-vim-config-with-pathogen</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-13323</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Wed, 16 Mar 2011 03:07:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-13323</guid>
		<description>1)Yep, your absolutely right, 7.2 here. The vim -version did not show me any directory what so ever though.

2) That worked, I create the .vim and colors folder and now it&#039;s working, I think it had something to do with the :set runtimepath? that did not have the path to where I was placing the colors before, but it did was the ~/ path.

One last question, for the plugins, like nerdTree, sparkup and others, should I also put them now inside the new ~/.vim/ folder and create inside a plugin folder like I did with the colors or those should be in another place like etc or usr for vim.</description>
		<content:encoded><![CDATA[<p>1)Yep, your absolutely right, 7.2 here. The vim -version did not show me any directory what so ever though.</p>
<p>2) That worked, I create the .vim and colors folder and now it&#8217;s working, I think it had something to do with the :set runtimepath? that did not have the path to where I was placing the colors before, but it did was the ~/ path.</p>
<p>One last question, for the plugins, like nerdTree, sparkup and others, should I also put them now inside the new ~/.vim/ folder and create inside a plugin folder like I did with the colors or those should be in another place like etc or usr for vim.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Wyatt</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-13309</link>
		<dc:creator>Derek Wyatt</dc:creator>
		<pubDate>Wed, 16 Mar 2011 00:08:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-13309</guid>
		<description>A few things :)

1) You can&#039;t be using 7.6 - it looks like you&#039;re using 7.2, but if you&#039;re not then putting things in /usr/share/vim/vim72 won&#039;t help you because that&#039;s clearly for version 7.2.  Typing vim --version will show you what directory that Vim is interested in.
2) the absolute simplest way to get a colour scheme working in your personal environment is to stick it in ~/.vim/colors
3) Your font probably isn&#039;t right.  The simplest thing to do is type &#039;:set guifont=*&#039; and then use the font selector that pops up to choose your font.  Once it looks the way you want, and you&#039;ve closed the dialog, then type &#039;:set guifont&#039;.  You&#039;ll see how Vim has interpreted this and it will show you what you should put in your vimrc.</description>
		<content:encoded><![CDATA[<p>A few things :)</p>
<p>1) You can&#8217;t be using 7.6 &#8211; it looks like you&#8217;re using 7.2, but if you&#8217;re not then putting things in /usr/share/vim/vim72 won&#8217;t help you because that&#8217;s clearly for version 7.2.  Typing vim &#8211;version will show you what directory that Vim is interested in.<br />
2) the absolute simplest way to get a colour scheme working in your personal environment is to stick it in ~/.vim/colors<br />
3) Your font probably isn&#8217;t right.  The simplest thing to do is type &#8216;:set guifont=*&#8217; and then use the font selector that pops up to choose your font.  Once it looks the way you want, and you&#8217;ve closed the dialog, then type &#8216;:set guifont&#8217;.  You&#8217;ll see how Vim has interpreted this and it will show you what you should put in your vimrc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-13297</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Tue, 15 Mar 2011 20:31:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-13297</guid>
		<description>Hi derek, I&#039;m having problems with my vimrc, I&#039;m using gvim ver 7.6, in Ubuntu Maverick latest Ver. I&#039;ve created the .vimrc from inside gvim and saved it in my home and changed the colorscheme plus the font to a custome &quot;Monospace:12&quot; but then when I launch gvim it shows errors then I press enter and gvim opens anyway, but the font is way letterspaced the font is wrong and the theme is not showing, I have placed all the colorschemes in /usr/share/vim/vim72/colors cause I wasn&#039;t sure If I should created a colors folder in my home vim folder. 
any direccions would be appreciated, thanks.

Error:
An error has been detected when processing /home/danilux/.vimrc:
line    3
E185: can&#039;t find colorscheme anotherDark</description>
		<content:encoded><![CDATA[<p>Hi derek, I&#8217;m having problems with my vimrc, I&#8217;m using gvim ver 7.6, in Ubuntu Maverick latest Ver. I&#8217;ve created the .vimrc from inside gvim and saved it in my home and changed the colorscheme plus the font to a custome &#8220;Monospace:12&#8243; but then when I launch gvim it shows errors then I press enter and gvim opens anyway, but the font is way letterspaced the font is wrong and the theme is not showing, I have placed all the colorschemes in /usr/share/vim/vim72/colors cause I wasn&#8217;t sure If I should created a colors folder in my home vim folder.<br />
any direccions would be appreciated, thanks.</p>
<p>Error:<br />
An error has been detected when processing /home/danilux/.vimrc:<br />
line    3<br />
E185: can&#8217;t find colorscheme anotherDark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Sinclair</title>
		<link>http://www.derekwyatt.org/vim/the-vimrc-file/comment-page-1/#comment-7256</link>
		<dc:creator>Rick Sinclair</dc:creator>
		<pubDate>Wed, 08 Dec 2010 17:28:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.derekwyatt.org/?page_id=20#comment-7256</guid>
		<description>For me, it proved a little more difficult due to some settings for the 256 color and also calling that xoria256.vim from within both the vim and gvim.  This link had nice instructions: http://www.vim.org/scripts/script.php?script_id=2140

Read you vimrc file.  Very nice of you to share that hard-earned work and discovery.  Thanks, Derek!</description>
		<content:encoded><![CDATA[<p>For me, it proved a little more difficult due to some settings for the 256 color and also calling that xoria256.vim from within both the vim and gvim.  This link had nice instructions: <a href="http://www.vim.org/scripts/script.php?script_id=2140" rel="nofollow">http://www.vim.org/scripts/script.php?script_id=2140</a></p>
<p>Read you vimrc file.  Very nice of you to share that hard-earned work and discovery.  Thanks, Derek!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

