From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3) with ESMTP id UAA28023 for ; Fri, 31 May 1996 20:27:50 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id GAA08060; Fri, 31 May 1996 06:16:02 -0400 (EDT) Resent-Date: Fri, 31 May 1996 06:16:02 -0400 (EDT) To: schaefer@z-code.ncd.com cc: Zoltan Hidvegi , zsh-workers@math.gatech.edu Subject: Re: execcmd() reordering In-reply-to: Your message of "Thu, 30 May 1996 12:52:37 -0700." Date: Fri, 31 May 1996 11:15:35 +0100 Message-ID: <9992.833537735@dis.strath.ac.uk> From: Duncan Sinclair Resent-Message-ID: <"Q3tPn3.0.sz1.YRihn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/1237 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu "Barton E. Schaefer" writes: >On May 30, 9:10pm, Zoltan Hidvegi wrote: >} Subject: Re: execcmd() reordering >} >} > When you've got a *huge* expansion which is 50% of the run-time >} > of the command, I'd like to be able to get on with other things. >} >} You can use (foo **/*) & > >I tend to agree with Duncan here, I'm afraid. I may not have any idea >how large a list the glob is going to expand into; it's ridiculous to >expect me to subshell every command that might do a glob. > >Furthermore, it'd be really nice to be able to stop (^Z) an unexpectedly >huge glob and then "bg" it, or to interrupt it with ^C if I decide it was >a mistake. Oh, absolutely! Does this change mean I can't interrupt long globs??? This would be terrible - esp. if the glob goes into a loop. All the other things, I can live with. This gives me nightmares. Bye for now, Duncan.