All of lore.kernel.org
 help / color / mirror / Atom feed
From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] pkeys.7: ffix
Date: Mon, 10 Jan 2022 19:49:45 +0100	[thread overview]
Message-ID: <20220110184945.x74zfpgt7enrrqta@tarta.nabijaczleweli.xyz> (raw)
In-Reply-To: <738c0961-b640-cad3-524e-79f7903aacdc@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]

Hi!

On Mon, Jan 10, 2022 at 07:13:48PM +0100, Alejandro Colomar (man-pages) wrote:
> On 1/9/22 17:21, наб wrote:
> > Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> > ---
> >   man7/pkeys.7 | 4 +---
> >   1 file changed, 1 insertion(+), 3 deletions(-)
> > 
> > diff --git a/man7/pkeys.7 b/man7/pkeys.7
> > index 73ddcdc43..0fff6493f 100644
> > --- a/man7/pkeys.7
> > +++ b/man7/pkeys.7
> > @@ -42,9 +42,7 @@ to change the contents of a register in order to remove write
> >   access, or all access to a tagged page.
> >   .PP
> >   Protection keys work in conjunction with the existing
> > -.BR PROT_READ /
> > -.BR PROT_WRITE /
> > -.BR PROT_EXEC
> > +.BR PROT_READ / PROT_WRITE / PROT_EXEC
> 
> It's not that your formatting seems worse to me in this case.
> 
> However, since we already have some kind of norm of writing each identifier
> on its own line, I'll keep it like that for consistency.
> That consistency also helps write scripts to find some patterns.
The problem with that is, of course, that it looks, uh, Not Good
(and that's already quite generous).
Hardly a good use of a typesetting language.

There's two ways to go about this, both keeping one symbol per line
(which, I do agree, is quite nice; the scriptability concern is somewhat
 misplaced, IMO, given man(7)-imposed limitations, but.).

1. Keeping the current /-based flow:
     Protection keys work in conjunction with the existing
     .BR PROT_READ / \
     PROT_WRITE / \
     PROT_EXEC
     permissions passed to system calls such as
   (This sets as my original patch: "isting [P_R]/[P_W]/[P_E] permiss".)

2. Reorienting as a list:
     Protection keys work in conjunction with the existing
     .BR PROT_READ ,
     .BR PROT_WRITE ", and"
     .BR PROT_EXEC
     permissions passed to system calls such as
   (Which sets as "existing [P_R], [P_W], and [P_E] permissions".)

IMO, 2 reads better. Thoughts?

наб

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-01-10 18:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 16:21 [PATCH] pkeys.7: ffix наб
2022-01-10 18:13 ` Alejandro Colomar (man-pages)
2022-01-10 18:49   ` наб [this message]
2022-01-11 18:17     ` Alejandro Colomar (man-pages)
2022-01-11 18:27       ` [PATCH v2 1/2] pkeys.7: wfix наб
2022-01-11 18:31         ` Alejandro Colomar (man-pages)
2022-01-11 18:28       ` [PATCH v2 2/2] glob.3: srcfix наб
2022-01-11 18:47         ` Alejandro Colomar (man-pages)

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=20220110184945.x74zfpgt7enrrqta@tarta.nabijaczleweli.xyz \
    --to=nabijaczleweli@nabijaczleweli.xyz \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.