public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org,
	 branden@debian.org
Subject: Re: Issue in man page getpt.3
Date: Thu, 25 Dec 2025 14:20:36 +0100	[thread overview]
Message-ID: <aU05v_HKTPPwb71k@devuan> (raw)
In-Reply-To: <aUv64tskHbjzCiMI@meinfjell.helgefjelltest.de>

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

Hi Helge,

On Wed, Dec 24, 2025 at 02:38:26PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    multiplexor → multiplexer

I see both used:

	$ grep -rho multiplex.r man/ | sort| uniq -c
	      4 multiplexer
	      4 multiplexor

Which one should we prefer, and why?

I don't know if any one is more correct than the other, as I'm not
a native English speaker.


Have a lovely day!
Alex

> 
> "B<getpt>()  opens a new pseudoterminal device and returns a file descriptor "
> "that refers to that device.  It is equivalent to opening the pseudoterminal "
> "multiplexor device"
> 
> "on Linux systems, though the pseudoterminal multiplexor device is located "
> "elsewhere on some systems that use the GNU C library."

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

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

  reply	other threads:[~2025-12-25 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 14:38 Issue in man page getpt.3 Helge Kreutzmann
2025-12-25 13:20 ` Alejandro Colomar [this message]
2025-12-25 13:22   ` Alejandro Colomar
2025-12-25 21:05     ` G. Branden Robinson
2025-12-25 21:20       ` Alejandro Colomar
  -- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
2025-08-31 16:36 ` Alejandro Colomar
2025-08-31 16:53   ` Helge Kreutzmann

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=aU05v_HKTPPwb71k@devuan \
    --to=alx@kernel.org \
    --cc=branden@debian.org \
    --cc=debian@helgefjell.de \
    --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