<?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: Editing PowerShell Scripts with VIM</title>
	<atom:link href="http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/feed/" rel="self" type="application/rss+xml" />
	<link>http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/</link>
	<description></description>
	<lastBuildDate>Sun, 21 Mar 2010 09:43:35 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bart</title>
		<link>http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/comment-page-1/#comment-1017</link>
		<dc:creator>Bart</dc:creator>
		<pubDate>Mon, 30 Nov 2009 03:36:51 +0000</pubDate>
		<guid isPermaLink="false">http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/#comment-1017</guid>
		<description>Does anyone know if it is it possible to use vim to edit a text file on a remote machine when logged in via PowerShell (i.e. via new-pssession)? Or if there is any alternative way to do this?</description>
		<content:encoded><![CDATA[<p>Does anyone know if it is it possible to use vim to edit a text file on a remote machine when logged in via PowerShell (i.e. via new-pssession)? Or if there is any alternative way to do this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tag cloud generator</title>
		<link>http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/comment-page-1/#comment-784</link>
		<dc:creator>tag cloud generator</dc:creator>
		<pubDate>Sat, 22 Aug 2009 21:44:53 +0000</pubDate>
		<guid isPermaLink="false">http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/#comment-784</guid>
		<description>In this blog, I forget my usual habit and I post things here!</description>
		<content:encoded><![CDATA[<p>In this blog, I forget my usual habit and I post things here!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kruger</title>
		<link>http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/comment-page-1/#comment-241</link>
		<dc:creator>Michael Kruger</dc:creator>
		<pubDate>Tue, 06 Jan 2009 21:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/#comment-241</guid>
		<description>Thanks for the information on editing scripts with VIM. I was curious whether anyone had created a syntax highlighting plugin for Powershell. If it provides help for omni-completion, that would be very cool. Will check it out. 

BTW...There are now x64 binaries available for VIM version 7.2. It&#039;s a command line installer, but seems to work fine in Vista x64. 

http://code.google.com/p/vim-win3264/wiki/Win64Binaries</description>
		<content:encoded><![CDATA[<p>Thanks for the information on editing scripts with VIM. I was curious whether anyone had created a syntax highlighting plugin for Powershell. If it provides help for omni-completion, that would be very cool. Will check it out. </p>
<p>BTW&#8230;There are now x64 binaries available for VIM version 7.2. It&#8217;s a command line installer, but seems to work fine in Vista x64. </p>
<p><a href="http://code.google.com/p/vim-win3264/wiki/Win64Binaries" rel="nofollow">http://code.google.com/p/vim-win3264/wiki/Win64Binaries</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dwight</title>
		<link>http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/comment-page-1/#comment-167</link>
		<dc:creator>dwight</dc:creator>
		<pubDate>Thu, 06 Nov 2008 22:01:29 +0000</pubDate>
		<guid isPermaLink="false">http://get-powershell.com/2008/11/06/editing-powershell-scripts-with-vim/#comment-167</guid>
		<description>i&#039;ve got real issues with unicode using VIM and powershell scripts. not pretty.</description>
		<content:encoded><![CDATA[<p>i&#8217;ve got real issues with unicode using VIM and powershell scripts. not pretty.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
