<?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: Filenames Starting with a Dot</title>
	<atom:link href="http://winterdom.com/2008/02/filenamesstartingwithadot/feed" rel="self" type="application/rss+xml" />
	<link>http://winterdom.com/2008/02/filenamesstartingwithadot</link>
	<description>by dæmons be driven</description>
	<lastBuildDate>Tue, 16 Mar 2010 06:33:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2008/02/filenamesstartingwithadot/comment-page-1#comment-141</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Wed, 26 Mar 2008 15:25:24 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/02/filenamesstartingwithadot#comment-141</guid>
		<description>George: I wasn&#039;t singling VIM out, just using it as an example. And I do understand it was because of old FAT compatibility and stuff like that (which does make you wonder how long we&#039;ll carry that noose around our necks). And, btw, thanks for all the work on VIM :)
</description>
		<content:encoded><![CDATA[<p>George: I wasn&#8217;t singling VIM out, just using it as an example. And I do understand it was because of old FAT compatibility and stuff like that (which does make you wonder how long we&#8217;ll carry that noose around our necks). And, btw, thanks for all the work on VIM <img src='http://winterdom.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George V. Reilly</title>
		<link>http://winterdom.com/2008/02/filenamesstartingwithadot/comment-page-1#comment-140</link>
		<dc:creator>George V. Reilly</dc:creator>
		<pubDate>Tue, 25 Mar 2008 23:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/02/filenamesstartingwithadot#comment-140</guid>
		<description>I wrote a lot of the Vim Win32 console mode code back in the mid-90s. If I remember correctly, NT 3.x supported FAT-16. I&#039;m pretty sure Win95 (cursed be its name) did. And Bram had a policy at the time of trying to unify the Win32 and the DOS codebases as much as possible. A filename like .vimrc wouldn&#039;t have worked on FAT-16.
(Or something like that. I had to page these memories back in from tape, where they were stored with a lossy compressor.)
</description>
		<content:encoded><![CDATA[<p>I wrote a lot of the Vim Win32 console mode code back in the mid-90s. If I remember correctly, NT 3.x supported FAT-16. I&#8217;m pretty sure Win95 (cursed be its name) did. And Bram had a policy at the time of trying to unify the Win32 and the DOS codebases as much as possible. A filename like .vimrc wouldn&#8217;t have worked on FAT-16.<br />
(Or something like that. I had to page these memories back in from tape, where they were stored with a lossy compressor.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2008/02/filenamesstartingwithadot/comment-page-1#comment-139</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Tue, 11 Mar 2008 15:17:56 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/02/filenamesstartingwithadot#comment-139</guid>
		<description>I&#039;m far more surprised that setting is still enabled by default on Windows Server 2008.
</description>
		<content:encoded><![CDATA[<p>I&#8217;m far more surprised that setting is still enabled by default on Windows Server 2008.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flatliner</title>
		<link>http://winterdom.com/2008/02/filenamesstartingwithadot/comment-page-1#comment-138</link>
		<dc:creator>Flatliner</dc:creator>
		<pubDate>Tue, 11 Mar 2008 15:13:08 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/02/filenamesstartingwithadot#comment-138</guid>
		<description>Oh totally agree on that point, I also think it&#039;s a security risk to hide file extensions from users. (remember the old .vbs attachment viruses?). I was really hoping that setting would be off in Vista by default as part of MS&#039;s whole &quot;secure by default&quot; strategy. Sadly not.
</description>
		<content:encoded><![CDATA[<p>Oh totally agree on that point, I also think it&#8217;s a security risk to hide file extensions from users. (remember the old .vbs attachment viruses?). I was really hoping that setting would be off in Vista by default as part of MS&#8217;s whole &quot;secure by default&quot; strategy. Sadly not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2008/02/filenamesstartingwithadot/comment-page-1#comment-137</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Mon, 10 Mar 2008 15:42:13 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/02/filenamesstartingwithadot#comment-137</guid>
		<description>@Flatliner: That might very well be true; but, heck, I *always* disable that option as soon as I install windows; it&#039;s the most stupid setting anyone ever came up with.
</description>
		<content:encoded><![CDATA[<p>@Flatliner: That might very well be true; but, heck, I *always* disable that option as soon as I install windows; it&#8217;s the most stupid setting anyone ever came up with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flatliner</title>
		<link>http://winterdom.com/2008/02/filenamesstartingwithadot/comment-page-1#comment-136</link>
		<dc:creator>Flatliner</dc:creator>
		<pubDate>Mon, 10 Mar 2008 15:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/02/filenamesstartingwithadot#comment-136</guid>
		<description>I believe Windows Explorer disallows filenames starting with a . because it&#039;s default setting of hiding File Extensions.
It deems .txt (for example) as just an extension so nothing would show after you named a file like this.
</description>
		<content:encoded><![CDATA[<p>I believe Windows Explorer disallows filenames starting with a . because it&#8217;s default setting of hiding File Extensions.<br />
It deems .txt (for example) as just an extension so nothing would show after you named a file like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2008/02/filenamesstartingwithadot/comment-page-1#comment-135</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Mon, 25 Feb 2008 15:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/02/filenamesstartingwithadot#comment-135</guid>
		<description>Wasn&#039;t ASP.NET the one causing trouble? At least I remember reading something about it, though never caused me any trouble (or maybe it is IIS, trying to figure out the right mime type for it or something).
Either way, anyway you look at it, it is those tools/apps that are broken; not the file system semantics.
</description>
		<content:encoded><![CDATA[<p>Wasn&#8217;t ASP.NET the one causing trouble? At least I remember reading something about it, though never caused me any trouble (or maybe it is IIS, trying to figure out the right mime type for it or something).<br />
Either way, anyway you look at it, it is those tools/apps that are broken; not the file system semantics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien Guard</title>
		<link>http://winterdom.com/2008/02/filenamesstartingwithadot/comment-page-1#comment-134</link>
		<dc:creator>Damien Guard</dc:creator>
		<pubDate>Mon, 25 Feb 2008 15:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/02/filenamesstartingwithadot#comment-134</guid>
		<description>Visual Studio 2003 used to be very troublesome with .folders and files which was a real pain as Subversion created .svn folders for the metadata by default.
Most Windows based Subversion tools had the ability to switch this over to _svn for exactly that reason.
[)amien
</description>
		<content:encoded><![CDATA[<p>Visual Studio 2003 used to be very troublesome with .folders and files which was a real pain as Subversion created .svn folders for the metadata by default.<br />
Most Windows based Subversion tools had the ability to switch this over to _svn for exactly that reason.<br />
[)amien</p>
]]></content:encoded>
	</item>
</channel>
</rss>
