From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: `jobs | wc -l' => 0 ... bug?
Date: Mon, 26 Mar 2001 17:04:07 +0000 [thread overview]
Message-ID: <Tc0a88d0152888bd0a5@mailsweeper01.cambridgesiliconradio.com> (raw)
In-Reply-To: Your message of "Mon, 26 Mar 2001 16:48:37 GMT." <1010326164837.ZM13050@candle.brasslantern.com>
> On Mar 26, 3:29pm, Peter Stephenson wrote:
> } Subject: Re: `jobs | wc -l' => 0 ... bug?
> }
> } > $ jobs | wc -l
> } > 0
> }
> } jobs here runs in a subshell, where there is no job control, so no
> } information on jobs. It has always been this way. It's not particularly
> } convenient, however. Maybe it's time someone thought about changing it.
>
> What do you suggest, that we special-case the "jobs" command?
Clearing the job table is handled specially in entersubsh().
if (cl)
clearjobtab();
MONITOR gets unset at this point, too. It shouldn't be necessary to do
both, and it should be possible to hack bin_fg() so that it can still list
jobs even if it can't control them. In fact, it looks like this is half
there: `fg' and `bg' test for !jobbing and complain, whereas `jobs'
doesn't and silently scans the empty job list. So maybe not clearing the
job table and relying on the option setting just works. But it needs a
proper work through to make sure.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
next prev parent reply other threads:[~2001-03-26 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 15:18 Adam Spiers
2001-03-26 15:29 ` Peter Stephenson
2001-03-26 16:48 ` Bart Schaefer
2001-03-26 17:04 ` Peter Stephenson [this message]
2001-03-27 13:13 ` Adam Spiers
2001-03-26 15:33 ` Thomas Köhler
2001-03-27 6:54 Sven Wischnowsky
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=Tc0a88d0152888bd0a5@mailsweeper01.cambridgesiliconradio.com \
--to=pws@csr.com \
--cc=zsh-workers@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).