> Daniel James wrote:
>>> The only thing I can see is the <F1>. Will this cause a problem?
>>>
>>
>> I would expect so, considering that > and < have special meanings in the
>> bash shell. For example, attempt to create a file with <F1> in the name:
>>
>> dan...@64studio:~$ touch <F1>test
>> bash: F1: No such file or directory
>>
>
> Using the correct syntax handling this special characters shouldn't be
> an issue for any application: $ touch \<F1\>
> File names are allowed to use any sign excepted the /, NUL, * and ? in
> Linux file names. I don't know any trick to handle the - as first sign
> for a file name:
>
> $ ls -al
> -rw-r--r-- 1 spinymouse-sudo spinymouse-sudo 5 2010-05-14 11:35 -n
>
> E.g. try to run $ cat ;). It might be better not to use the - as first
> sign.
>
> Apart from that I couldn't find information about forbidden signs for
> Linux file names. If < and > aren't allowed when using Ardour, Ardour
> should inform about it and ban those signs. IMO this would be a
> serious issue and should be reported to Ardour devs.
Correction:
spinymouse-s...@64studio:~$ cat ./-n
test
spinymouse-s...@64studio:~$ cat -n ./-n
1 test
spinymouse-s...@64studio:~$ rm ./-n
Using the - as first sign shouldn't cause trouble. But I guess using the
$-sign could cause an issue.
_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users
