Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Linux/Unix naming conventions...



On Thu, 23 Dec 1999, Seth Gordon wrote:

> Not to disagree, but to supplement: some utilities assume, by default,
> that file names don't have any spaces in them.  (For example, they

Tecnically, this is not true, though practically speaking the result is
the same. The unix utilities make no assumptions about spaces in
filenames.  It is the shells that will ordinarily assume that spaces
separate filenames (or arguments of any kind). To tell the shell that an
argument has a space in it, you need only put quotes around it.  This is
how you can get your utilities to use filenames with spaces in them.

I still recommend against using them, but there are lots of less-educated
Windows people that will put spaces in their filenames.  I can't tell you
how much frustration that has caused...

-- 
Derek D. Martin
Senior UNIX Systems/Network Administrator
Arris Interactive
derek.martin at ne.arris-i.com

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org