From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] blanks in names
Date: Fri, 5 Jul 2002 07:29:22 +0900 [thread overview]
Message-ID: <20020704222938.D726119980@mail.cse.psu.edu> (raw)
In-Reply-To: <20020704164128.8041219988@mail.cse.psu.edu>
>i agree that it should be visible; but i also think it should be
>visually distinguishable as a "spacer" character (i.e. not a peter
>face)
How about x7f ?
However these discussions are meaningless if we quote file name
whenever spaces are contained,
Genuine space code is best for internal code.
Kenji Arisawa
next prev parent reply other threads:[~2002-07-04 22:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 16:47 rog
2002-07-04 17:06 ` FJ Ballesteros
2002-07-04 22:29 ` arisawa [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-04 19:41 rob pike, esq.
2002-07-04 6:47 forsyth
2002-07-04 19:45 ` rob pike, esq.
2002-07-04 14:56 ` FJ Ballesteros
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=20020704222938.D726119980@mail.cse.psu.edu \
--to=arisawa@ar.aichi-u.ac.jp \
--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).