Re: QOUTES
From: Jeremiah DeWitt Weiner (jdw_at_panix.com)
Date: 01/13/05
- Previous message: Alan Connor: "Re: The art of reading man pages"
- In reply to: Chris F.A. Johnson: "Re: QOUTES"
- Next in thread: Chris F.A. Johnson: "Re: QOUTES"
- Reply: Chris F.A. Johnson: "Re: QOUTES"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 13 Jan 2005 21:58:12 +0000 (UTC)
Chris F.A. Johnson <cfajohnson@gmail.com> wrote:
> It's also not a good idea to use spaces or colons in file names.
Sun might disagree with you about the colons.
Dbsera1:~$ ls /devices/
pci@1f,2000:devctl pci@4,2000:devctl pci@6,2000:devctl pseudo
Also stuff like /etc/hostname.hme0:1. Admittedly, those are not
files one has to deal with often, or that the average user ever has to
deal with.
Come to think of it, why _do_ you recommend against colons in
filenames? I agree that it seems odd and nonstandard, but it doesn't
actually seem to cause much of a problem in practice. Bash doesn't list
it as either a metacharacter or a control operator, although a colon in
a filename does get escaped by autocompletion (and breaks autocompletion
if you've typed it in yourself without escaping it, although failure to
escape the colon doesn't seem to cause any harm.) I suppose that's
because it's a path separator - having a directory with a colon in its
name in your PATH does break things, but I'd argue that if you do something
as weird as that, you deserve whatever you get.
JDW
- Previous message: Alan Connor: "Re: The art of reading man pages"
- In reply to: Chris F.A. Johnson: "Re: QOUTES"
- Next in thread: Chris F.A. Johnson: "Re: QOUTES"
- Reply: Chris F.A. Johnson: "Re: QOUTES"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|