Re: Square brackets in file names and authz (in VisualSVN 2.5.5)

On 2012/07/11, at 20:20, David Brodbeck wrote:

> On Wed, Jul 11, 2012 at 8:01 AM, Matthew Pounsett <matt_at_conundrum.com> wrote:
>> I note by your examples that you're using a unix filesystem (as opposed to Windows). I would be a little surprised if this worked there, since the square brackets are normally used by unix shells as glob metacharacters, similarly to * and ?.
>
> Just because they're used as shell metacharacters doesn't mean they
> aren't legal in filenames:

Right, but anything using simple methods of globbing may not react well to their use, as the OP seems to have discovered. I didn't say you couldn't force the files to be created, just that I'd be a little surprised if those characters worked in authz configs.

That said.. it turns out the OP is on Windows after all, and I was just fooled by the non-windows notation for the file names. I'm no authority on what is or isn't possible on NTFS since I haven't touched it in a good 10+ years so it's likely none of what I had to say applies to his problem.

>
>>> It's also worth pointing out that some paths have the "#" character in them. What do I do when I get to those?
>>
>> This is commonly comment character. It's possible to create a file with this character in it, but personally I'd avoid it. It's possible you could escape it like so: "tmp\#1.txt", but I'm not confident that will work. If svn can't deal with this one you might have a case for it being a bug, since it is technically a legal file name.
>
> emacs uses files starting and ending in "#" extensively for autosave
> recovery data, FWIW.

Again, didn't say it wasn't possible.. just that it might not be well advised.
Received on 2012-07-12 02:25:25 CEST