Path: utzoo!utgpu!water!watmath!clyde!att!ihnp4!chinet!les
From: les@chinet.UUCP (Leslie Mikesell)
Newsgroups: comp.unix.wizards
Subject: Re: Kernel Hacks & Weird Filenames
Message-ID: <5572@chinet.UUCP>
Date: 12 May 88 04:17:40 GMT
References: <13041@brl-adm.ARPA> <4895@chinet.UUCP> <574@minya.UUCP> <24@csnz.nz> <52768@sun.uucp>
Reply-To: les@chinet.UUCP (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 19

In article <52768@sun.uucp> guy@gorodish.Sun.COM (Guy Harris) writes:
>> Does that mean that a naive user can make a file with a 
>> in the name?
>Yup.  As I presume you mean to imply, those names would be considered quite
>valid by some users.  Many such users won't necessarily be using the
>traditional UNIX shells, so it might not be at all inconvenient to use names
>containing spaces.

Users with a "point-and-click" interface wouldn't be bothered at all by
that.  Never mind that it breaks a lot of the administrators file management
shell scripts...
Off the subject, but an interesting side effect I have noticed of the
point-and-click type interface is that users tend to use longer filenames
and more mixed-case names.  Being harder to type is not a real disadvantage
since the name is only typed when the file is created.  Very interesting
things happen when you try to put directories full of long mixed-case
names into an MSDOS network-server environment.
  
  Les Mikesell