From: Peter Stephenson <p.stephenson@samsung.com>
To: 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 09:45:49 +0000 [thread overview]
Message-ID: <20171220094549.1d755d1a@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20171220085620.76561c93@zam158.zam.kfa-juelich.de>
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...
jobs [ -dlprs ] [ job ... ]
jobs -Z string
Lists information about each given job, or all jobs if job is
omitted. The -l flag lists process IDs, and the -p flag lists
process groups. If the -r flag is specified only running jobs
will be listed and if the -s flag is given only stopped jobs are
shown. If the -d flag is given, the directory from which the
job was started (which may not be the current directory of the
job) will also be shown.
The -Z option replaces the shell's argument and environment
space with the given string, truncated if necessary to fit.
This will normally be visible in ps (ps(1)) listings. This fea‐
ture is typically used by daemons, to indicate their state.
There's no mention of *only* listing process groups.
pws
next prev parent reply other threads:[~2017-12-20 9:46 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 [this message]
2017-12-20 10:42 ` Eric Pruitt
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=20171220094549.1d755d1a@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=matthias.richerzhagen@alumni.fh-aachen.de \
--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).