From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spaces in file/dir names? (and acme)?
Date: Wed, 5 Jun 2002 09:55:14 +0000 [thread overview]
Message-ID: <3CF7E56E.4998FF02@null.net> (raw)
In-Reply-To: <20020530190313.U22942@cackle.proxima.alt.za>
Lucio De Re wrote:
> ... I suppose the word delimiter on the command line could have
> been something less convenient...
That just changes the symptoms.
For fully general processing of "arguments" in the presence of
special-character handling, some form of "escape" is necessary
to prevent unwanted special-character handling. However, that
in general also requires use of an additional special character.
Just one character can suffice to escape a whole raft of s.c.s.
It helps immensely if different apps that might be used in
conjunction employ *different* escapes (and s.c.s); if you have
ever seen a Unix shell script generating a troff macro, with
perhaps 16 \s in a row needed to get it to collapse to one \ at
the stage where it is needed, you can appreciate the problem.
next prev parent reply other threads:[~2002-06-05 9:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 16:57 Fco.J.Ballesteros
2002-05-30 17:03 ` Lucio De Re
2002-06-05 9:55 ` Douglas A. Gwyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 10:29 Fco.J.Ballesteros
2002-06-06 10:48 ` Axel Belinfante
2002-06-06 8:11 Fco.J.Ballesteros
2002-06-06 10:22 ` Axel Belinfante
2002-06-05 18:39 Geoff Collyer
2002-06-05 17:55 rog
2002-06-05 17:04 anothy
2002-06-05 13:46 Russ Cox
2002-06-03 7:48 Fco.J.Ballesteros
2002-06-03 16:05 ` Dan Cross
2002-06-05 10:05 ` Douglas A. Gwyn
2002-06-01 21:37 jmk
2002-06-01 22:06 ` Dan Cross
2002-05-30 22:01 forsyth
2002-05-30 20:16 rog
2002-05-30 20:14 rsc
2002-05-30 19:29 rog
2002-05-30 19:12 forsyth
2002-05-30 18:58 rog
2002-05-30 18:55 rsc
2002-05-30 18:16 rog
2002-06-04 16:23 ` Axel Belinfante
2002-05-30 18:15 rsc
2002-05-30 18:13 Geoff Collyer
2002-05-31 4:53 ` Lucio De Re
2002-05-31 8:59 ` Boyd Roberts
2002-05-30 18:09 Sape Mullender
2002-05-30 17:58 Fco.J.Ballesteros
2002-05-30 17:10 ` Sam
2002-05-30 17:52 presotto
2002-05-30 17:46 Geoff Collyer
2002-05-30 17:00 Fco.J.Ballesteros
2002-06-01 21:34 ` Dan Cross
2002-05-30 16:30 rsc
2002-05-30 16:35 ` Axel Belinfante
2002-06-05 9:54 ` Douglas A. Gwyn
2002-05-30 16:30 rsc
2002-05-30 16:21 Axel Belinfante
2002-05-30 16:27 ` Boyd Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CF7E56E.4998FF02@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).