Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!cmcl2!yale!husc6!rutgers!lll-crg!ames!ucbcad!ucbvax!jade!eris!mwm
From: mwm@eris.BERKELEY.EDU (Mike (Don't have strength to leave) Meyer)
Newsgroups: comp.sys.amiga
Subject: Democracy in Action (for K keys: more pattern matching flames)
Message-ID: <1966@jade.BERKELEY.EDU>
Date: Tue, 16-Dec-86 23:04:25 EST
Article-I.D.: jade.1966
Posted: Tue Dec 16 23:04:25 1986
Date-Received: Thu, 18-Dec-86 03:46:29 EST
References: <1108@spice.cs.cmu.edu> <1696@vax135.UUCP>
Sender: usenet@jade.BERKELEY.EDU
Reply-To: mwm@eris.BERKELEY.EDU (Mike (Don't have strength to leave) Meyer)
Organization: Missionaria Phonibalonica
Lines: 27

In article <1696@vax135.UUCP> cjp@vax135.UUCP (Charles Poirier) writes:
>While I'm at it, let me add my vote in favor of uniform filename
>expansion at the CLI level.

Marvelous. Let's vote in favor of something you don't understand! To wit:

>By the way, this should be tweaked in a way that UNIX screws up: for
>output-redirection, i.e. cmd >foo#?.  ALLOW globbing IF the expansion
>results in ONE file name (error otherwise).

Sorry, but you *CAN* get Unix to do exactly that. You have to remember
that it's mindlessly expanding arguments into file names, so you have
to make the output (or input) file a separate word, as "cmd > foo*".
Works like a charm. It even returns the error "ambiguous" when there's
more than one file.

The thing that annoys me most about all this is that much of the
discussion - including mine - is based on assumptions that are correct
for a 9600 baud or slower terminal tied to a serial line, but wrong
for the Amiga. I've been designing a shell that ignores those (and
shows a change in my position).

I'll post something ASAP for the world to comment on, but I'm under
time pressure to get 4.3BSD ported to our 8800. It's hard to do
anything as long as a shell design during kernel compiles :-).