Not *exactly* a bug, but ...

Not *exactly* a bug, but ...

[Bart Schaefer]

I think I may have reported this before, a very long time ago ...

zsh% fc -W >(....)

This locks up zsh.  You have to HUP it from another shell (or from the
xterm ctrl-btn1 menu) to kill it; there's no way to wake it up.

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

Re: Not *exactly* a bug, but ...

[gwing]

Bart Schaefer wrote:
:I think I may have reported this before, a very long time ago ...
:zsh% fc -W >(....)

This for specific commands?  It works for me, eg.  fc -W >(cat)
Are you getting this both in older and newer versions?
zsh-3.0.0 up to 3.0.3-test3 work on my NetBSD machine.

:This locks up zsh.  You have to HUP it from another shell (or from the
:xterm ctrl-btn1 menu) to kill it; there's no way to wake it up.
-- 
Geoff Wing [gwing@primenet.com.au]   Technical Manager
  Phone    : +61-3-9818 2977         PrimeNet - Internet Consultancy
  Facsimile: +61-3-9819 3788         Web : <URL:http://www.primenet.com.au/>
  Mobile   : 0412 162 441

Re: Not *exactly* a bug, but ...

[Bart Schaefer]

On Feb 17,  1:44am, gwing@primenet.com.au wrote:
} Subject: Re: Not *exactly* a bug, but ...
}
} Bart Schaefer wrote:
} :I think I may have reported this before, a very long time ago ...
} :zsh% fc -W >(....)
} 
} This for specific commands?  It works for me, eg.  fc -W >(cat)

Hmm.  Looks like it only locks up if you use -I, e.g., fc -WI >(cat) is
one of the commands that locks up for me.  I thought I'd tried it both
with and without -I, but maybe I'd only tried both -W and -A with -I.

} Are you getting this both in older and newer versions?

Yes, if I put the -I in there.


-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern