Chris Snook wrote:Jack Stone wrote:H. Peter Anvin wrote:I can escape the semicolon just fine in bash. In fact, tab-completionChris Snook wrote:But that would cause havoc with shells which use ; to seperate commands.I pointed out NetApp's .snapshot directories because that's a methodNot to mention that the character historically used for this purpose is
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught that : is suddenly a
special character.
; (semicolon.)
Using ; would defiantly break userspace
Jack
will do this automatically. That's really a non-issue. It just means
that anyone who wants to use this feature would have to know what
they're doing, which I believe is your goal, right?
I didn't realise this. Would ; break userspace if it was used as the
delimiter?
This discussion may be academic as this design is looking less and less
useful/workable.