public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page session-keyring.7
Date: Sun, 22 Jan 2023 21:52:34 +0100	[thread overview]
Message-ID: <1fdc5117-5858-9c8b-d64b-340a53fb8ea3@gmail.com> (raw)
In-Reply-To: <20230122200844.au2yezkhalgk44n7@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --]

Hi Branden, Helge:

On 1/22/23 21:08, G. Branden Robinson wrote:
> Hi Helge,
> 
> At 2023-01-22T20:31:30+0100, Helge Kreutzmann wrote:
>> Without further ado, the following was found:
>>
>> Issue:    What does "under others" mean? Is this a special hook? Or does this mean "amongst other actions done by this command"?
>>
>> "If a process doesn't have a session keyring when it is accessed, then, under"
>> "certain circumstances, the B<user-session-keyring>(7)  will be attached as"
>> "the session keyring and under others a new session keyring will be created."
>> "(See B<user-session-keyring>(7)  for further details.)"
> 
> It seems idiomatic to me.
> 
> Under certain circumstances, I wake up in the morning.
> Under others [other circumstances], I awaken after noon.

I believe a semicolon would be a better way to connect both sentences.  "and", 
considering the amount of commans in the context, doesn't help very much parsing 
the sentence.

What do you think?

Cheers,

Alex

P.S.: The colon in the salutation is the standard way in Spanish :)

> 
> Regards,
> Branden

-- 
<http://www.alejandro-colomar.es/>

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

  parent reply	other threads:[~2023-01-22 20:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 19:31 Issue in man page session-keyring.7 Helge Kreutzmann
2023-01-22 20:08 ` G. Branden Robinson
2023-01-22 20:34   ` Helge Kreutzmann
2023-01-22 20:52   ` Alejandro Colomar [this message]
2023-01-22 20:56     ` G. Branden Robinson
  -- strict thread matches above, loose matches on Subject: below --
2023-03-11 17:13 Helge Kreutzmann
2023-03-11 22:24 ` Alejandro Colomar
2023-03-12  4:57   ` Helge Kreutzmann
2023-03-12 12:18     ` Alejandro Colomar
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 20:59 ` Alejandro Colomar

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=1fdc5117-5858-9c8b-d64b-340a53fb8ea3@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.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