From: Eric Pruitt <eric.pruitt@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Matthias Richerzhagen <matthias.richerzhagen@alumni.fh-aachen.de>,
zsh-workers@zsh.org
Subject: Re: `jobs -p` does not behave as documented and required by POSIX
Date: Wed, 20 Dec 2017 02:42:05 -0800 [thread overview]
Message-ID: <20171220104205.5p7g46ajt4knhmfg@sinister.lan.codevat.com> (raw)
In-Reply-To: <20171220094549.1d755d1a@pwslap01u.europe.root.pri>
On Wed, Dec 20, 2017 at 09:45:49AM +0000, Peter Stephenson wrote:
> On Wed, 20 Dec 2017 08:56:20 +0100
> Matthias Richerzhagen <matthias.richerzhagen@alumni.fh-aachen.de> wrote:
> > Hello,
> >
> > the manpage for the `jobs` buildin function states:
> >
> > > −p Display only the process IDs for the process group
> > > leaders of the selected jobs.
> >
> > > STDOUT
> > > If the −p option is specified, the output shall consist of one
> > > line for each process ID:
> > >
> > > "%d\n", <process ID>
>
> Erm, I don't think you're looking at the right manual...
The text Matthias is quoting is from the POSIX specification
(http://pubs.opengroup.org/onlinepubs/009695399/utilities/jobs.html). I
think their point is moot though because Z-shell does not claim to be
POSIX compliant in its default mode. That said, when running Z-shell as
"sh", the output of `jobs -p` still includes the "extra" information:
~$ (exec -a sh zsh -c 'sleep 1 & sleep 2 & jobs -p')
[1] - 1022 running sleep 1
[2] + 1023 running sleep 2
Eric
next prev parent reply other threads:[~2017-12-20 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171220080716epcas1p14317a75dd17abfa9d127ef341bcc383b@epcas1p1.samsung.com>
2017-12-20 7:56 ` Matthias Richerzhagen
2017-12-20 9:45 ` Peter Stephenson
2017-12-20 10:42 ` Eric Pruitt [this message]
2017-12-20 11:49 ` dana
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=20171220104205.5p7g46ajt4knhmfg@sinister.lan.codevat.com \
--to=eric.pruitt@gmail.com \
--cc=matthias.richerzhagen@alumni.fh-aachen.de \
--cc=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/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).