9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug or a feature?
Date: Wed, 12 Jun 2002 08:53:54 +0000	[thread overview]
Message-ID: <3D064187.EFE0CC96@null.net> (raw)
In-Reply-To: <66556c53bb0f92dac0b0484edeef3f8d@plan9.bell-labs.com>

"rob pike, esq." wrote:
> This is long-standard behavior for shells.  Feature.

Indeed, but since so many other aspects of Unix were rethought
for Plan 9, it deserves some consideration; it's certainly
contrary to simplicity and regularity.  Perhaps someone knows
the history of this decision, but my *guess* is that it was
deemed to be more useful in "typical" interactive use:
	% cp foo.* bar
	cp: foo.*: nonexistent file
As of 6th Edition Unix there was a separate "glob" utility.

For some purposes, e.g. find . whatever -print | xargs ...
I find myself providing an extra argument "/dev/null" to
the command invoked under xargs control; e.g. when it's
"grep" and I want to be sure to see the filename even if
the grep is invoked with just one filename argument (that
works around an irregularity in "grep", again likely to be
due to thinking about interactive use).  Too bad there is
nothing similar that could be used as an "empty string"
placeholder.  (I introduced that notion in the 1999 C
standard as part of the specification for handling empty
arguments to function-like macros, and it made it easy to
be sure that the empty arguments didn't vanish until we
really wanted them to.)


  parent reply	other threads:[~2002-06-12  8:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11 15:29 rob pike, esq.
2002-06-11 21:05 ` andrey mirtchovski
2002-06-11 21:19   ` Ronald G Minnich
2002-06-12  5:17     ` Lucio De Re
2002-06-12  8:53 ` Douglas A. Gwyn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-27 20:30 Byron Rakitzis
2002-07-27 12:10 presotto
2002-07-27  2:43 Byron Rakitzis
2002-06-13 23:05 Russ Cox
2002-06-13 23:23 ` Dan Cross
2002-06-13 20:35 Russ Cox
2002-06-13 20:58 ` Dan Cross
2002-06-13 21:34   ` Tharaneedharan Vilwanathan
2002-06-13  3:41 Russ Cox
2002-06-13  1:01 Russ Cox
2002-06-13 17:40 ` Dan Cross
2002-06-12 23:49 Geoff Collyer
2002-06-13  0:07 ` Dan Cross
2002-06-13  0:31 ` Pavel Mihaylov
2002-06-13  2:29 ` Lyndon Nerenberg
     [not found] <dmr@plan9.bell-labs.com>
2002-06-12 19:57 ` Dennis Ritchie
2002-06-12 20:16   ` Scott Schwartz
2002-06-12 19:52 andrey mirtchovski
2002-06-12 21:57 ` Dan Cross
2002-06-12 22:53   ` Lyndon Nerenberg
2002-06-14  8:45     ` Douglas A. Gwyn
2002-06-14 16:23       ` Lyndon Nerenberg
2002-06-12  9:15 forsyth
2002-06-13  9:29 ` Douglas A. Gwyn
2002-06-11 15:32 Russ Cox
2002-06-11 15:26 andrey mirtchovski
2002-06-11 15:14 andrey mirtchovski

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=3D064187.EFE0CC96@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).