linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Wilk <jwilk@jwilk.net>
To: Rick Stanley <rstanley@rsiny.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: Re: Man page pre & post operators error
Date: Fri, 20 Sep 2019 19:00:42 +0200	[thread overview]
Message-ID: <20190920170042.444behwks42xvs6a@jwilk.net> (raw)
In-Reply-To: <a1683c1cc450bf969aca13d8f7a99f08cc07635d.camel@rsiny.com>

* Rick Stanley <rstanley@rsiny.com>, 2019-09-20, 10:19:
>In the man pages, both in Linux and online in multiple sites, the pre 
>and post operators are listed as equal precedence.  Two different web 
>sites list them on different levels:
>
>http://man7.org/linux/man-pages/man7/precedence.7.html
>	Level 1
>
>https://linux.die.net/man/7/operator
>	Level 2

FWIW, they are not on different levels. In fact, the operator tables are 
identical; the only difference is that the one on linux.die.net is badly 
formatted.

In general, I would recommend avoiding linux.die.net. Their manpages are 
often out-of-date, but you can't easily tell, because they removed 
version information.

-- 
Jakub Wilk

  reply	other threads:[~2019-09-21  0:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 14:19 Man page pre & post operators error Rick Stanley
2019-09-20 17:00 ` Jakub Wilk [this message]
2019-09-22 21:01 ` Michael Kerrisk (man-pages)
2019-09-22 22:50   ` Rick Stanley
2019-09-23  7:43     ` Michael Kerrisk (man-pages)
2019-09-25 15:23     ` Rick Stanley
2019-09-25 19:42       ` Michael Kerrisk (man-pages)
2019-09-25 20:08         ` Michael Kerrisk (man-pages)
2019-09-25 22:53           ` Rick Stanley
2019-09-28 18:05         ` Manpage operator update Rick Stanley
2019-10-01 13:48         ` proposed patch to operator manpage Rick Stanley

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=20190920170042.444behwks42xvs6a@jwilk.net \
    --to=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=rstanley@rsiny.com \
    /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.
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).