Zsh Mailing List Archive
Messages sorted by:
Re: zsh: Strange feature with 'jobs' commmand
- X-seq: zsh-workers 17260
- From: Oliver Kiddle <okiddle@xxxxxxxxxxx>
- To: Zsh workers <zsh-workers@xxxxxxxxxx>
- Subject: Re: zsh: Strange feature with 'jobs' commmand
- Date: Thu, 30 May 2002 14:26:53 +0100
- In-reply-to: <Pine.SV4.4.44.0205301632500.21658-100000@xxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <Pine.SV4.4.44.0205301632500.21658-100000@xxxxxxxxxxxxxxxxxxxxx>
- Sender: kiddleo@xxxxxxxxxx
On 30 May, you wrote:
> > Incidentally, I think bash special cases the jobs builtin and would
> > run less in a subshell in this case instead. Could we do something like
> IIRC bash runs right part of every pipe in subshell. We run left pipe.
I think I have read something about a special case on a newsgroup
somewhere. A quick grep in the bash sources reveals a jobs_hack variable
which has a comment saying that it is there to allow jobs to be piped
but that may be solving some other issue.
> This makes it possible to do something like
> foo | read FOO_RESULT
ksh93 manages to do both this and piped output from jobs so it must be
possible. I just think it is a bit crap that it doesn't work because it
will take anyone who doesn't know by surprise.
> Anyway, I am afraid, changing it requires quite a major rewrite. And in
Tricks like jobs > >(cat -) sort-of work so I was thinking a special
case hack for jobs might not need a big rewrite. But I've never gone
near that part of zsh's code so wouldn't know.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
Messages sorted by: