9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave <dave@dave.tj>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Mon,  8 Jul 2002 16:58:40 -0400	[thread overview]
Message-ID: <200207082058.g68Kwgi23131@dave2.dave.tj> (raw)
In-Reply-To: <c0b4788df08e5315718331288f5e0c34@plan9.bell-labs.com>

...not even ... if you s/ /_/g all incoming filenames, you'll have no
way of distinguishing 'a b' from 'a_b' ... or am I wrong?

 - Dave


rob pike, esq. wrote:
> 
> This is a multi-part message in MIME format.
> --upas-hysbwqswxskaflauqaypshypxy
> Content-Disposition: inline
> Content-Type: text/plain; charset="US-ASCII"
> Content-Transfer-Encoding: 7bit
> 
> 99% only.  You'd still have the problem of names that arrive surreptitiously,
> such as in tar files.
> 
> -rob
> 
> --upas-hysbwqswxskaflauqaypshypxy
> Content-Type: message/rfc822
> Content-Disposition: inline
> 
> Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Mon Jul  8 12:06:16 EDT 2002
> Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Mon Jul  8 12:06:15 EDT 2002
> Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.18.6])
> 	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
> 	id 7F994199BC; Mon,  8 Jul 2002 12:06:08 -0400 (EDT)
> Delivered-To: 9fans@cse.psu.edu
> Received: from nautilus.escet.urjc.es (nautilus.escet.urjc.es [212.128.4.207])
> 	by mail.cse.psu.edu (CSE Mail Server) with SMTP id C8D81199B9
> 	for <9fans@cse.psu.edu>; Mon,  8 Jul 2002 12:05:05 -0400 (EDT)
> Message-ID: <8aeb5e383c12f6b44b043e969d203fb5@plan9.escet.urjc.es>
> From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
> MIME-Version: 1.0
> Content-Type: multipart/mixed;
> 	boundary="upas-gtvahntgehtrsxxskbyfbulvvm"
> Sender: 9fans-admin@cse.psu.edu
> Errors-To: 9fans-admin@cse.psu.edu
> X-BeenThere: 9fans@cse.psu.edu
> X-Mailman-Version: 2.0.11
> Precedence: bulk
> Reply-To: 9fans@cse.psu.edu
> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
> List-Archive: <https://lists.cse.psu.edu/archives/9fans/>
> Date: Mon, 8 Jul 2002 18:05:03 +0200
> 
> This is a multi-part message in MIME format.
> --upas-gtvahntgehtrsxxskbyfbulvvm
> Content-Disposition: inline
> Content-Type: text/plain; charset="US-ASCII"
> Content-Transfer-Encoding: 7bit
> 
> Renaming them would get us quickly up to 100%, with no need
> to fix anything. Am I wrong?
> --upas-gtvahntgehtrsxxskbyfbulvvm
> Content-Type: message/rfc822
> Content-Disposition: inline
> 
> Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Mon Jul  8 18:01:23 MDT 2002
> Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6])
> 	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
> 	id 1D95B19995; Mon,  8 Jul 2002 12:01:13 -0400 (EDT)
> Delivered-To: 9fans@cse.psu.edu
> Received: from plan9.cs.bell-labs.com (ampl.com [204.178.31.2])
> 	by mail.cse.psu.edu (CSE Mail Server) with SMTP id 7A9F519991
> 	for <9fans@cse.psu.edu>; Mon,  8 Jul 2002 12:00:11 -0400 (EDT)
> Message-ID: <a5b373bbdc70b762911c083da046ca5f@plan9.bell-labs.com>
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
> From: "rob pike, esq." <rob@plan9.bell-labs.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset="US-ASCII"
> Content-Transfer-Encoding: 7bit
> Sender: 9fans-admin@cse.psu.edu
> Errors-To: 9fans-admin@cse.psu.edu
> X-BeenThere: 9fans@cse.psu.edu
> X-Mailman-Version: 2.0.11
> Precedence: bulk
> Reply-To: 9fans@cse.psu.edu
> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
> List-Archive: <https://lists.cse.psu.edu/archives/9fans/>
> Date: Mon, 8 Jul 2002 12:00:09 -0400
> 
> > Glub! My first view of all this blank thing was just to forbid
> > them and maybe rename them just to avoid them (They make things more
> > complex for our programs). 
> 
> I encounter a dozen blank-containing names a day, but only from
> interacting with foreign systems.  I find the current setup covers about
> 80% of what I need; fixing a few other simple things would probably
> get us to 99%.  But upon reflection I don't think it's wise to push for
> blanks to be first-class citizens in file names.  As long as we continue
> to use linguistic rather than graphical interfaces to most of our tools,
> that would be a mistake.
> 
> -rob
> 
> --upas-gtvahntgehtrsxxskbyfbulvvm--
> --upas-hysbwqswxskaflauqaypshypxy--
> 



  reply	other threads:[~2002-07-08 20:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 16:07 rob pike, esq.
2002-07-08 20:58 ` Dave [this message]
2002-07-08 22:18   ` arisawa
  -- strict thread matches above, loose matches on Subject: below --
2002-07-10  7:57 Fco.J.Ballesteros
2002-07-09 12:24 Fco.J.Ballesteros
2002-07-09  9:37 Fco.J.Ballesteros
2002-07-09  8:42 Fco.J.Ballesteros
2002-07-09  9:28 ` Lucio De Re
2002-07-09 11:23   ` andrey mirtchovski
2002-07-09 12:05     ` matt
     [not found] ` <Fco.J.Ballesteros@Jul>
2002-07-09 15:29   ` Dave
2002-07-10 15:57   ` Dave
2002-07-09  8:40 Fco.J.Ballesteros
2002-07-09  7:50 Fco.J.Ballesteros
2002-07-09  8:15 ` Lucio De Re
2002-07-09  8:42   ` arisawa
2002-07-09  9:21     ` Lucio De Re
2002-07-09  9:43       ` arisawa
2002-07-09 10:36         ` Lucio De Re
2002-07-09 10:54           ` matt
     [not found]     ` <"arisawa@ar.aichi-u.ac.jp"@Jul>
2002-07-09 15:31       ` Dave
2002-07-09 22:15         ` arisawa
2002-07-09  8:22 ` arisawa
2002-07-09  7:46 Fco.J.Ballesteros
2002-07-09  0:38 okamoto
2002-07-08 16:14 rob pike, esq.
2002-07-08 16:05 Fco.J.Ballesteros
2002-07-08 16:00 rob pike, esq.
2002-07-08 15:51 Fco.J.Ballesteros
2002-07-08 15:42 rob pike, esq.
2002-07-08 15:18 Fco.J.Ballesteros
2002-07-08 15:16 rob pike, esq.
2002-07-08 15:10 Fco.J.Ballesteros
2002-07-08 15:16 ` Lucio De Re
2002-07-08 14:54 Fco.J.Ballesteros
2002-07-08 15:05 ` Lucio De Re

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=200207082058.g68Kwgi23131@dave2.dave.tj \
    --to=dave@dave.tj \
    --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).