At 12:51 PM +0200 6/8/00, Samuel Tardieu wrote:
>On  8/06, Jeroen Ruigrok van der Werven wrote:
>| -On [20000608 03:12], Kris Kennaway ([EMAIL PROTECTED]) wrote:
>| >Instead of using only alphabetic characters, the patch uses the following
>| >character set:
>| >
>| >0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~
>| >
>| > which is not believed to cause any problems with shells.
>| Some shells parse # as a deletion character if memory serves me right.
>| I think I noticed this behaviour when I started using zsh a few weeks
>| ago after ksh.
>Also ^ is used for substitutions in many shells (as in ^faulty^ok).

I believe bash requires some kind of whitespace character (blank,
tab, newline) in front of the '#' before it will treat it as the
comment character.  I am not sure about other shells (people who
use other shells might want to check).

Similarly, I believe '^' is used for substitutions ONLY if it is
the first character in the line.  Ie, 'echo hello^to^you' does
not do any substitution on the previous line.

Since we know these characters are only being used in a filename,
and NOT as the first character of a filename, then we should not
have trouble using them.

I must admit I am not as comfortable using '+=,', and I think one
of '@' or ':' should go, just in case the file is used in some
context that reads blah@blah:blah as userid@hostname:fname
I would probably drop the '@', but if there is some other reason
to drop ':' then the '@' could probably stay.

At the same time, I do like to see the set expanded as much as
possible, without causing any problems.

Garance Alistair Drosehn           =   [EMAIL PROTECTED]
Senior Systems Programmer          or  [EMAIL PROTECTED]
Rensselaer Polytechnic Institute

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to