[M3devel] [M3commit] CVS Update: cm3

[Mika Nystrom]

I never tried putting it in my PATH, no... You are right, colons
are *slightly* special.  I am not in the habit of copying files to
Windows.  I only copy files between Unix and Windows to save them
from Windows.

That being said, I am pretty sure I use colons more in filenames
than I use the letter "q".  Could you ban the letter "q" instead?  :)

If you've gotta do it, then do it.  It's just ... weird.

I personally will probably never run into the issue.  I use colons
in filenames a lot, but as a separator for various types of data
files.  <data source>:<data details>.<extension>

Is your code able to import (or duplicate...) Pathname?  I would
have thought that that interface has all the necessary bits to make
paths portable...

     MIka

Jay writes:
>--_dfd4e29a-b904-43be-8435-4824d419d270_
>Content-Type: text/plain; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
>> But colons? Colons are not special in any way, shape, or form, on> Unix..=
>. I think "it is extremely surprising" to a Unix user if a path
>Ever try putting a path with a colon into $PATH? Does it work?
>Or copying a file with a colon in its name to a Windows system? Does it wor=
>k?
>This part could be limited to systems that have $OS =3D=3D Windows_NT I gue=
>ss.
>=20
>As a user switching between multiple systems, this area is quite frustratin=
>g...I guess no matter what.
>Sometimes one form works, sometimes another, sometimes either, often with i=
>dentical meaning, but not always.
>These changes, and about one more, should make building NT386GNU a fair amo=
>unt easier..
>=20
>Currently it is any path with a colon in the second character.
>How about if that is further restricted to having a-z in the first characte=
>r and/or more importantly a slash in the third character?
>=20
> - Jay
>
>
>