<?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>edeca.net &#187; vim</title>
	<atom:link href="http://edeca.net/wp/tag/vim/feed/" rel="self" type="application/rss+xml" />
	<link>http://edeca.net/wp</link>
	<description>Musings of a geek</description>
	<lastBuildDate>Tue, 14 Feb 2012 00:18:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>vim vs. Linux extended ACLs</title>
		<link>http://edeca.net/wp/2009/08/vim-vs-linux-extended-acls/</link>
		<comments>http://edeca.net/wp/2009/08/vim-vs-linux-extended-acls/#comments</comments>
		<pubDate>Sun, 02 Aug 2009 12:55:53 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[vim]]></category>

		<guid isPermaLink="false">http://staging.edeca.net/wp/?p=177</guid>
		<description><![CDATA[Extended ACLs on Linux can be incredibly useful.  Permissions can actually be more secure whilst allowing a number of users or daemons access to a file, no longer are unwieldy groups necessary to allow reading or writing.  But for some reason, I noticed that these extended ACLs disappeared when a file was edited in vim. [...]]]></description>
			<content:encoded><![CDATA[<p>Extended ACLs on Linux can be incredibly useful.  Permissions can actually be more secure whilst allowing a number of users or daemons access to a file, no longer are unwieldy groups necessary to allow reading or writing.  But for some reason, I noticed that these extended ACLs disappeared when a file was edited in vim.<span id="more-177"></span></p>
<p>The solution is very simple, you just need to <tt>set backupcopy=yes</tt> in your <tt>.vimrc</tt>.  Note that <tt>backupcopy=auto</tt> currently does <strong>not</strong> work.</p>
<p>The way that vim normally works is to rename the file you are working on and write a new file.  This is fast and means that no files have to be deleted.  Unfortunately, it also means that any special attributes that vim does not understand are lost.</p>
<p>Setting <tt>backupcopy=yes</tt> ensures that the original file is copied and then overwritten upon save.  This takes a little longer, but will preserve the attributes correctly.  More information can be found in the topic <tt>:help backupcopy</tt> inside vim.</p>
<p>You can check <a href="http://articles.techrepublic.com.com/5100-10878_11-6091748.html">this page</a> for a quick rundown or <a href="http://www.suse.de/~agruen/acl/linux-acls/online/">this one</a> for a longer explanation on how ACLs work in Linux.</p>
]]></content:encoded>
			<wfw:commentRss>http://edeca.net/wp/2009/08/vim-vs-linux-extended-acls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

