9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: FJ Ballesteros <nemo@gsyc.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] blanks in names
Date: Thu,  4 Jul 2002 16:56:53 +0200	[thread overview]
Message-ID: <3D246235.40CCB6E9@gsyc.escet.urjc.es> (raw)
In-Reply-To: <1110399.1025797535@GOLD>



"rob pike, esq." ha escrito:
> I enabled blanks because they kept appearing, everyone else accepts
> them, and it seemed a challenge to find a good solution.  I still
> prefer the quoting solution because it leaves the underlying stuff
> alone, but it's easier to just say no.
> 
> -rob

Before you enabled them, I just said no.
Now that I have been able to use external names, I wouldn't want
to go back. I think you did a very good thing just by considering
the problem and trying to solve it; please, don't look back :-)


  reply	other threads:[~2002-07-04 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-04  6:47 forsyth
2002-07-04 19:45 ` rob pike, esq.
2002-07-04 14:56   ` FJ Ballesteros [this message]
2002-07-04 16:47 rog
2002-07-04 17:06 ` FJ Ballesteros
2002-07-04 22:29 ` arisawa
2002-07-04 19:41 rob pike, esq.

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=3D246235.40CCB6E9@gsyc.escet.urjc.es \
    --to=nemo@gsyc.escet.urjc.es \
    --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).