From: Pavol Juhas <juhas@pa.msu.edu>
To: zsh-users@sunsite.dk
Subject: Re: problem piping output of shell builtin
Date: Mon, 5 Jan 2004 15:36:38 -0500 [thread overview]
Message-ID: <20040105203638.GA9567@pa.msu.edu> (raw)
In-Reply-To: <Pine.NEB.4.58.0401051856430.2690@norge.freeshell.org>
On Mon, Jan 05, 2004 at 07:26:15PM +0000, gj@sdf.lonestar.org wrote:
> Hi all,
>
> I'm migrating from bash to zsh. It hasn't been so bad because I'm sort of new
> to shell programming anyways ( though I did have "fun" figuring out that zsh
> arrays start incrementing from 1 as opposed to bash's 0 :). I thought I'd
> share the latest hiccup...
>
> Why can't I pipe the output of 'jobs' thusly?
AFAIK, all the shells run one side of the pipe in a subshell. bash
executes subshell for the right side of the pipe, however zsh does
so for the left side. Therefore the `jobs' command in
`jobs|read line' is evaluated in the subshell of zsh, which has no
knowledge about processes in the parent shell - and produces no
output. Left side subshell is however advantageous in other
situations, just compare
zsh -c 'echo 10|read a; echo .$a'
.10
bash -c 'echo 10|read a; echo .$a'
.
To access information in the zsh job table, you need to use the
builtin associate arrays jobtexts, jobstates and jobdirs, for example:
for j in ${(k)jobstates}; do
print -- "[$j] ${jobstates[$j]} ${jobtexts[$j]} in ${jobdirs[$j]}"
done
HTH,
Pavol
next prev parent reply other threads:[~2004-01-05 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 19:26 gj
2004-01-05 20:36 ` Pavol Juhas [this message]
2004-01-05 21:30 ` Vincent Stemen
2004-01-06 1:24 ` Bart Schaefer
2004-01-06 1:39 ` Pavol Juhas
2004-01-05 20:44 ` Vincent Stemen
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=20040105203638.GA9567@pa.msu.edu \
--to=juhas@pa.msu.edu \
--cc=zsh-users@sunsite.dk \
/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).