[SVN] overlapping fileTypes in multiple bundles?

[Brian Lalor]

On Jan 5, 2005, at 5:49 AM, Allan Odgaard wrote:

> On Jan 5, 2005, at 11:10, Brian Lalor wrote:
>
>> How does TM handle having a single file extension set in the 
>> fileTypes property in multiple bundles? [...]
>
> It uses the first match (where 'first' is undefined ;) ). If the user 
> manually selects a syntax highlight for a loaded file, TM will 
> remember this binding, so the extensions in the bundles are just 
> defaults.

Is that stored per-file or per-extension?

>> Allan, do you intend to support something like Emacs' embedded mode 
>> specifier (I just made that up; sounds good, doesn't it? :-) ), such 
>> as
>> 	// -*- XML -*-
>> to indicate that a given file should use that mode?
>
> I haven't considered it, but at least for tab size it sounds like a 
> good idea. With regard to modes, is there many cases where file 
> extension is not enough to decide the mode?

.plists. :-)

Also, various places where you might want to set wrapping preferences 
or modes in a .txt file.  Maybe if you want a more specific (or 
non-public) mode/bundle for a certain flavor of .xml document.

>> [...] why password-protect the repository for anonymous access?
>
> Because I didn't know how to give anonymous read access :) But I'd 
> like to change it.

This is the entirety of the block in my httpd.conf that defines my 
subversion repository:
	<Location /svn/repos>
	   DAV svn
	   SVNPath /usr/local/svn/repos
	
	   # Limit write permission to list of valid users.
	   <LimitExcept GET PROPFIND OPTIONS REPORT>
	      # Require SSL connection for password protection.
	      # SSLRequireSSL
	
	      AuthType Basic
	      AuthName "Bravo5 Subversion Repository"
	      AuthUserFile /usr/local/svn/svn-auth-file
	      Require valid-user
	   </LimitExcept>
	</Location>

That grants anonymous access to people who want to perform GET, 
PROPFIND, OPTIONS and REPORT operations, but anything else requires a 
valid user.

> Before I do though (or at least before the URL gets announced) people 
> with stuff in the repository should be aware that it can then be 
> crawled by email-harvesting software, so I'd suggest to obfuscate 
> emails in README's etc.

I wondered if that might be your reasoning. :-)

-- 
    __   ____
   / /  / __/ Brian Lalor
  / _ \/__ \  blalor at bravo5.org
/_.__/____/  http://bravo5.org/