<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>LAMPlights &#187; vim</title>
	<atom:link href="http://www.hermanradtke.com/blog/tag/vim/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hermanradtke.com</link>
	<description>Personal anecdotes from my experiences using the LAMP stack</description>
	<lastBuildDate>Wed, 25 Jan 2012 18:14:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Frustration with vim.org</title>
		<link>http://www.hermanradtke.com/blog/frustration-with-vimorg/</link>
		<comments>http://www.hermanradtke.com/blog/frustration-with-vimorg/#comments</comments>
		<pubDate>Tue, 14 Apr 2009 01:02:37 +0000</pubDate>
		<dc:creator>Herman Radtke</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[docblock]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[vim]]></category>

		<guid isPermaLink="false">http://www.hermanradtke.com/blog/?p=50</guid>
		<description><![CDATA[I started using the phpDocumentor for Vim (PDV) script written by Tobias Schlitt.  Very quickly I found a bug with one of the regular expressions used to parse apart the class definition.  Tobias does not seem to be maintaing this plugin anymore, so I decided I would fix the bug and submit a new version [...]]]></description>
			<content:encoded><![CDATA[<p>I started using the phpDocumentor for Vim (PDV) script written by Tobias Schlitt.  Very quickly I found a bug with one of the regular expressions used to parse apart the class definition.  Tobias does not seem to be maintaing this plugin anymore, so I decided I would fix the bug and submit a new version to vim.org.  I packaged up the new version of the script and went to update the PDV page on vim.org only to find out I can't.  There isn't even a mechanism for me to post a comment.</p>
<p><span id="more-50"></span></p>
<p>I was frustrated to say the least, but knew I could not have been the first one.  I found an <a title=" Improvements for vim.org/scripts" href="http://www.mail-archive.com/vim_use@googlegroups.com/msg00456.html" target="_blank">archived email</a> sent by Thomas Koch to the VIM mailing list describing some of the problems with the management of scripts and the improvements he would like to see made.  Thomas also created a <a title="vim.org relaunch" href="http://vim.wikia.com/wiki/Vim.org_relaunch" target="_blank">wiki page</a> to organize his proposed relauch.</p>
<p>The great thing is that the website is built using PHP and MySQL.  That means I can lend a hand to make these changes happen.  I really don't want to see this project die off, so I have emailed the vim@vim.org mailing list prompting for more action.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hermanradtke.com/blog/frustration-with-vimorg/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Choosing VIM</title>
		<link>http://www.hermanradtke.com/blog/choosing-vim/</link>
		<comments>http://www.hermanradtke.com/blog/choosing-vim/#comments</comments>
		<pubDate>Sat, 11 Apr 2009 19:49:57 +0000</pubDate>
		<dc:creator>Herman Radtke</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[editor]]></category>
		<category><![CDATA[ide]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[vim]]></category>

		<guid isPermaLink="false">http://www.hermanradtke.com/blog/?p=36</guid>
		<description><![CDATA[At work we were using VIM for all editing, except PHP.  Back when the decision was made to use PHP for all web development, consultants told us we needed an IDE that offered all kinds of tools that VIM lacks.  So we shopped around for IDE's and eventually bought Zend Studio licenses for everyone.  Today [...]]]></description>
			<content:encoded><![CDATA[<p>At work we were using VIM for all editing, except PHP.  Back when the decision was made to use PHP for all web development, consultants told us we needed an IDE that offered all kinds of tools that VIM lacks.  So we shopped around for IDE's and eventually bought Zend Studio licenses for everyone.  Today those licesnses are collecting dust.  Even with the feature rich toolset of Zend Studio, and other IDE's, none seem to satisfy our need like VIM does.</p>
<p><span id="more-36"></span></p>
<p>I decided a few weeks ago that I would try to find the tools we liked in Zend Studio that were missing from VIM.  I know we didn't need things like version control integration or project management plugins.  The Linux command line is more than capable of handling these sorts of tasks.  And since most of us at work are Bash enthusiasts, doing it on the command line is often much faster.  What we needed were things like DocBlock generation and tag browsing.</p>
<p>I got started by referencing Thomas Kock's post on using <a title="VIM as a PHP IDE" href="http://www.koch.ro/blog/index.php?/archives/63-VIM-an-a-PHP-IDE.html" target="_blank">VIM as a PHP IDE</a>.  We already use cscope, so all the plugins he listed were pretty easy to introduce into our workflow.  The CodeSniffer integration is really sexy.  I did run into a problem with phpDocumentor for Vim.  It seems that Tobias Schlitt is no longer supporting that plugin.  Due to the ineffeciencies of vim.org, I moved the code over to <a href="http://github.com/hradtke/pdv/tree/master">github</a>.</p>
<p>I don't think VIM is the right PHP editor for everyone, but it has been working fairly well for us.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hermanradtke.com/blog/choosing-vim/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

