zsh-workers
 help / color / mirror / code / Atom feed
From: Duncan Sinclair <sinclair@dis.strath.ac.uk>
To: schaefer@z-code.ncd.com
Cc: Zoltan Hidvegi <hzoli@cs.elte.hu>, zsh-workers@math.gatech.edu
Subject: Re: execcmd() reordering
Date: Fri, 31 May 1996 11:15:35 +0100	[thread overview]
Message-ID: <9992.833537735@dis.strath.ac.uk> (raw)
In-Reply-To: Your message of "Thu, 30 May 1996 12:52:37 -0700."


"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.



             reply	other threads:[~1996-05-31 10:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-31 10:15 Duncan Sinclair [this message]
1996-05-31 10:55 ` Zoltan Hidvegi
1996-05-31 11:58   ` Peter Stephenson
1996-05-31 16:28     ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
1996-05-30 18:05 Duncan Sinclair
1996-05-30 19:10 ` Zoltan Hidvegi
1996-05-30 19:52   ` Barton E. Schaefer
1996-05-31 14:32     ` Hrvoje Niksic
1996-05-28 11:34 $(nooutput) problem Zoltan Hidvegi
1996-05-30 16:58 ` execcmd() reordering Peter Stephenson
1996-05-30 18:00   ` Zoltan Hidvegi
1996-05-30 18:26     ` Barton E. Schaefer
1996-05-30 18:46       ` Zoltan Hidvegi
1996-05-30 18:41     ` Zoltan Hidvegi

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=9992.833537735@dis.strath.ac.uk \
    --to=sinclair@dis.strath.ac.uk \
    --cc=hzoli@cs.elte.hu \
    --cc=schaefer@z-code.ncd.com \
    --cc=zsh-workers@math.gatech.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).