From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] experimental change for devmnt to deal with spaces
Date: Wed, 3 Jul 2002 16:45:33 +0200 [thread overview]
Message-ID: <20020703164533.D6107@cackle.proxima.alt.za> (raw)
In-Reply-To: <1771288.1025710997@GOLD>; from rob pike, esq. on Wed, Jul 03, 2002 at 03:43:19PM -0400
On Wed, Jul 03, 2002 at 03:43:19PM -0400, rob pike, esq. wrote:
>
> You are changing the meaning of the space character.
> Think about what that means, the number of places it
> affects, the impossibility of getting it right
> everywhere. This is a terrible idea.
>
I got it! Use whenever you need a non-breaking space, it's
a standard!
% touch 'a x'
will then create file 'a x'. Pity you still need quotes to escape the
'&' and ';' <grin>
++L
next prev parent reply other threads:[~2002-07-03 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 12:40 Fco.J.Ballesteros
2002-07-03 19:43 ` rob pike, esq.
2002-07-03 14:45 ` Lucio De Re [this message]
2002-07-03 15:42 ` FJ Ballesteros
2002-07-03 17:52 rog
2002-07-03 20:37 ` FJ Ballesteros
2002-07-03 21:38 rog
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=20020703164533.D6107@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).