<?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 Remote Files with VIM and SCP</title>
	<atom:link href="http://tipotheday.com/2008/06/08/editing-remote-files-with-vim-and-scp/feed/" rel="self" type="application/rss+xml" />
	<link>http://tipotheday.com/2008/06/08/editing-remote-files-with-vim-and-scp/</link>
	<description>techno tips and tricks</description>
	<lastBuildDate>Wed, 08 Sep 2010 21:43:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: webguy</title>
		<link>http://tipotheday.com/2008/06/08/editing-remote-files-with-vim-and-scp/comment-page-1/#comment-1992</link>
		<dc:creator>webguy</dc:creator>
		<pubDate>Thu, 05 Feb 2009 02:22:20 +0000</pubDate>
		<guid isPermaLink="false">http://tipotheday.com/?p=152#comment-1992</guid>
		<description>http://www.codeislove.org/?p=10
for a potential cygwin fix.</description>
		<content:encoded><![CDATA[<p><a href="http://www.codeislove.org/?p=10" rel="nofollow">http://www.codeislove.org/?p=10</a><br />
for a potential cygwin fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://tipotheday.com/2008/06/08/editing-remote-files-with-vim-and-scp/comment-page-1/#comment-1740</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Sun, 26 Oct 2008 22:34:15 +0000</pubDate>
		<guid isPermaLink="false">http://tipotheday.com/?p=152#comment-1740</guid>
		<description>&lt;code&gt;[[user@]host1:]file1&lt;/code&gt; from scp man page, so &lt;code&gt;gvim scp://user@host:/etc/profile&lt;/code&gt; would also work for a absolute path. And &lt;code&gt;gvim scp://user@host:.bash_profile&lt;/code&gt; for a relative path.

That whole u&lt;code&gt;ser@host//etc/profile, user@host/.bash_profile&lt;/code&gt; should be depreciated in my opinion.</description>
		<content:encoded><![CDATA[<p><code>[[user@]host1:]file1</code> from scp man page, so <code>gvim scp://user@host:/etc/profile</code> would also work for a absolute path. And <code>gvim scp://user@host:.bash_profile</code> for a relative path.</p>
<p>That whole u<code>ser@host//etc/profile, user@host/.bash_profile</code> should be depreciated in my opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randon</title>
		<link>http://tipotheday.com/2008/06/08/editing-remote-files-with-vim-and-scp/comment-page-1/#comment-1730</link>
		<dc:creator>Randon</dc:creator>
		<pubDate>Mon, 20 Oct 2008 16:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://tipotheday.com/?p=152#comment-1730</guid>
		<description>Has anyone used this from within Cygwin? I&#039;m trying to edit remote files on linux servers using a Windows laptop running Cygwin.

Unfortunately, I can&#039;t seem to get it to work. I get errors like &#039;can&#039;t open file for writing&#039; which seem like permission errors to me, but I don&#039;t know at this point.

I can do this just fine from another linux machine, but not from Windows using Cygwin.</description>
		<content:encoded><![CDATA[<p>Has anyone used this from within Cygwin? I&#8217;m trying to edit remote files on linux servers using a Windows laptop running Cygwin.</p>
<p>Unfortunately, I can&#8217;t seem to get it to work. I get errors like &#8216;can&#8217;t open file for writing&#8217; which seem like permission errors to me, but I don&#8217;t know at this point.</p>
<p>I can do this just fine from another linux machine, but not from Windows using Cygwin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wunar</title>
		<link>http://tipotheday.com/2008/06/08/editing-remote-files-with-vim-and-scp/comment-page-1/#comment-1469</link>
		<dc:creator>Wunar</dc:creator>
		<pubDate>Thu, 19 Jun 2008 02:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://tipotheday.com/?p=152#comment-1469</guid>
		<description>Well, it&#039;s not exactly like it *should* be followed. It&#039;s still
[scp://user@host/] [path] syntax, so you can use
scp://user@host/.vimrc perfectly fine, and it will take .vimrc from user&#039;s home folder (as path = .vimrc), and scp://user@host//etc/profile will specify full path to /etc/profile.</description>
		<content:encoded><![CDATA[<p>Well, it&#8217;s not exactly like it *should* be followed. It&#8217;s still<br />
[scp://user@host/] [path] syntax, so you can use<br />
scp://user@host/.vimrc perfectly fine, and it will take .vimrc from user&#8217;s home folder (as path = .vimrc), and scp://user@host//etc/profile will specify full path to /etc/profile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mshade</title>
		<link>http://tipotheday.com/2008/06/08/editing-remote-files-with-vim-and-scp/comment-page-1/#comment-1463</link>
		<dc:creator>mshade</dc:creator>
		<pubDate>Wed, 18 Jun 2008 02:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://tipotheday.com/?p=152#comment-1463</guid>
		<description>Thanks for the detail, Wunar -- And actually, omitting the : isn&#039;t all that&#039;s necessary.  Hostname should be followed by two //s.  Don&#039;t know how I missed that!  Thanks!

example:
vim scp://user@host//home/user/example.txt</description>
		<content:encoded><![CDATA[<p>Thanks for the detail, Wunar &#8212; And actually, omitting the : isn&#8217;t all that&#8217;s necessary.  Hostname should be followed by two //s.  Don&#8217;t know how I missed that!  Thanks!</p>
<p>example:<br />
vim scp://user@host//home/user/example.txt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wunar</title>
		<link>http://tipotheday.com/2008/06/08/editing-remote-files-with-vim-and-scp/comment-page-1/#comment-1461</link>
		<dc:creator>Wunar</dc:creator>
		<pubDate>Wed, 18 Jun 2008 01:55:21 +0000</pubDate>
		<guid isPermaLink="false">http://tipotheday.com/?p=152#comment-1461</guid>
		<description>After seeing weird errors, it occured to me that second colon in the address needs to be omitted, and used it only to specify the port for the scp connection, not like scp utility,

scp://user@host/foo/bar.txt
and
scp://user@host:9922/foo/bar.txt</description>
		<content:encoded><![CDATA[<p>After seeing weird errors, it occured to me that second colon in the address needs to be omitted, and used it only to specify the port for the scp connection, not like scp utility,</p>
<p>scp://user@host/foo/bar.txt<br />
and<br />
scp://user@host:9922/foo/bar.txt</p>
]]></content:encoded>
	</item>
</channel>
</rss>
