<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 11:21:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[DZone.com: 2 years of Vim and PHP distilled]]></title>
      <guid>http://www.phpdeveloper.org/news/17785</guid>
      <link>http://www.phpdeveloper.org/news/17785</link>
      <description><![CDATA[<p>
On DZone.com there's a new post from <i>Giorgio Sironi</i> with some of his tips for PHP developers that <a href="http://css.dzone.com/articles/2-years-vim-and-php-distilled">want to use VIM in their development</a> - some handy tricks to help make you a more effective developer.
</p>
<blockquote>
In the case of PHP development, you'll need to add some configuration and plugins to speed up your activities. Most of the responsibilities of an IDE - like testing and version control - are outsourced to the terminal while running Vim; however, there are some tweaks that make writing and editing code faster, along with aiding in discovery classes and methods in a PHP codebase.
</blockquote>
<p>
He includes settings for your .vimrc to detect and load the right PHP functionality, using <a href="https://wincent.com/products/command-t">Command-T</a>, functionality for autocompletion and the <a href="http://www.vim.org/scripts/script.php?script_id=2540">snipMate</a> plugin for managing and using reusable code snippets.
</p>]]></description>
      <pubDate>Fri, 06 Apr 2012 09:50:35 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Tobias Schlitt's Blog: PHP Documentor for VIM documented]]></title>
      <guid>http://www.phpdeveloper.org/news/6803</guid>
      <link>http://www.phpdeveloper.org/news/6803</link>
      <description><![CDATA[<p>
In <a href="http://schlitt.info/applications/blog/index.php?/archives/513-PHP-Documentor-for-VIM-documented.html">this new post</a> to his blog, <i>Tobias Schlitt</i> shares some VIM tips with the PHP community, specifically about PHP Documentor integration functionality. He's gone back and documented the functionality now to make it that much easier to use.
</p>
<blockquote>
Because I had a talk about <a href="http://schlitt.info/applications/blog/index.php?/archives/511-PHPUGDO-Upcoming-talks.html">how to use VIM in respect to PHP source code editing</a>, I took the time during the week, to write some extensive documentation for PDV, the PHP Documentor plugin for VIM.
</blockquote>
<p>
He's also documented the VIM file type plugin as well, and both are available through his <a href="http://svn.toby.phpugdo.de/PDV/">SVN of PDV</a>. There's also to updates mentioned - one about splitting up the .vimrc and file type plugin and added the repository to the official SVNServe list making it easy to check out.
</p>]]></description>
      <pubDate>Fri, 01 Dec 2006 07:15:18 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Bjarte Karlsen's Blog:  My vim setup for editing php files]]></title>
      <guid>http://www.phpdeveloper.org/news/6683</guid>
      <link>http://www.phpdeveloper.org/news/6683</link>
      <description><![CDATA[<p>
For those PHPers out there that use the vi editor for their coding travels, <i>Bjarte Karlsen</i> has <a href="http://phpmeus.blogspot.com/2006/11/my-vim-setup-for-editing-php-files.html">posted something</a> that might help you out - two configuration files that he uses to work with PHP files in vim.
</p>
<blockquote>
In a recent chat on #phpc we started discussing vim and talking about vim setups. Surripui posted a <a href="http://www.surripui.net/?p=39">blog entry about this</a> asking for setups. I promised that i would post my setup so here it is.
</blockquote>
<p>
The two files are his:
<ul>
<li><a href="http://www.pvv.org/~bjartka/vim/vimrc">.vimrc</a>
<li><a href="http://www.pvv.org/~bjartka/vim/php.vim">.vim/ftpplugin/php.vim</a>
</ul>
Between the two of these, the editor is able to correctly handle PHP files, syntax check files and tab complete function names. There's also a mention of using <a href="http://gonz.debianuruguay.org/hacks/gsnippets-0.2.txt">gsnippets</a> for working with code templates.
</p>]]></description>
      <pubDate>Fri, 10 Nov 2006 10:16:00 -0600</pubDate>
    </item>
  </channel>
</rss>
