All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.lists@gmail.com>
To: Oğuz <oguzismailuysal@gmail.com>,
	"mtk.manpages@gmail.com" <mtk.manpages@gmail.com>
Cc: Robert Elz <kre@munnari.oz.au>,
	austin-group-l <austin-group-l@opengroup.org>,
	"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
	linux-man <linux-man@vger.kernel.org>
Subject: Re: Pseudoterminal terminology in POSIX
Date: Tue, 11 Aug 2020 10:31:46 +0200	[thread overview]
Message-ID: <33583fda-da56-7f4c-caa3-08832f654707@gmail.com> (raw)
In-Reply-To: <CAH7i3LpXZxwaLQTY=XK8zM4jWYHSiy1feA6ZLE-mT-ZiJNak5A@mail.gmail.com>

[repairing CC]


On 8/6/20 6:53 AM, Oğuz via austin-group-l at The Open Group wrote:
> 5 Ağustos 2020 Çarşamba tarihinde Michael Kerrisk (man-pages) <
> mtk.lists@gmail.com> yazdı:
> 
>> On 8/5/20 7:12 PM, Oğuz via austin-group-l at The Open Group wrote:
>>> 5 Ağustos 2020 Çarşamba tarihinde Robert Elz via austin-group-l at The
>> Open
>>> Group <austin-group-l@opengroup.org> yazdı:
>>>
>>>>     Date:        Wed, 05 Aug 2020 11:28:45 -0400
>>>>     From:        "Paul Smith via austin-group-l at The Open Group" <
>>>> austin-group-l@opengroup.org>
>>>>     Message-ID:  <1d8c5e6e96fbdd47ce143a566b57d
>> b2c803d4898.camel@gnu.org>
>>>>
>>>>   | do you consider the pseudoterminal as providing to the terminal, or
>> the
>>>>   | terminal as providing to the pseudoterminal.
>>>>
>>>> How did anyone ever get to a question like that?  - there are a pair of
>>>> devices which between them implement a pseudo-terminal (which is just
>>>> like a terminal, to the application, but isn't one ... hence
>>>> pseudo-terminal).
>>>>
>>>> Personally I'm quite happy with the existing terminology, and see no
>>>> particular need for change (as close to meaningless as the terms are
>>>> in this context - they are well established, anything different will
>>>> just create confusion).
>>>>
>>>>
>>> Couldn't agree more. I don't understand what problem such a change in the
>>> terminology is supposed to solve.
>>
>> The problems have already been widely discussed elsewhere. For a
>> summary, see, for example, https://lwn.net/Articles/823224/
>>
>>
> I see, but changing well established, concrete terms with barely related,
> abstract, far-fetched alternatives just to make a bunch of oversensitive
> snowflakes doesn't make any sense (to me, at least).

Thanks for clarifying your perspective.

> If this change is going to happen no matter what we say, at least add a
> glossary somewhere for us non-native speakers where we can look up what
> each nonsensical alternative term actually means, unless you want to
> exclude us too, of course.

Some kind of change is pretty much inevitable. There are of course
already glossaries, in the form of documentation, and the standard.
The question is simply how to update these.

Thanks,

Michael


  parent reply	other threads:[~2020-08-11  8:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 11:21 Pseudoterminal terminology in POSIX Michael Kerrisk
2020-08-05 13:51 ` Steffen Nurpmeso
     [not found]   ` <20200805142049.GA17848@localhost>
2020-08-05 20:34     ` Michael Kerrisk (man-pages)
     [not found]     ` <CAP1RCkjrqKGJmh6f637D=yGuhev7ae5QJkMjv5a8iHo4X33NFw@mail.gmail.com>
     [not found]       ` <1d8c5e6e96fbdd47ce143a566b57db2c803d4898.camel@gnu.org>
2020-08-05 20:34         ` Michael Kerrisk (man-pages)
     [not found]         ` <21048.1596645536@jinx.noi.kre.to>
     [not found]           ` <CAH7i3LrNvBo3indixGyJgS2_4F9r3cd3kOiDgPK8m-ZXj1a0zg@mail.gmail.com>
     [not found]             ` <874bfe40-5f05-151d-42b3-482baacbf0b2@gmail.com>
     [not found]               ` <CAH7i3LpXZxwaLQTY=XK8zM4jWYHSiy1feA6ZLE-mT-ZiJNak5A@mail.gmail.com>
2020-08-11  8:31                 ` Michael Kerrisk (man-pages) [this message]
2020-08-08 23:18 ` Larry Dwyer
2020-08-10 13:20   ` Joerg Schilling
2020-08-10 18:10     ` Zack Weinberg
2020-08-10 18:17       ` Samuel Thibault
2020-08-10 18:21         ` Samuel Thibault
2020-08-11  8:32       ` Michael Kerrisk (man-pages)
2020-08-10 13:58   ` Thor Lancelot Simon
2020-08-11  8:31     ` Michael Kerrisk (man-pages)
2020-08-11 11:51       ` Thor Lancelot Simon
2020-08-11 14:20         ` Michael Kerrisk
2020-08-12 14:37       ` Thor Lancelot Simon
2020-08-11  8:32   ` Michael Kerrisk (man-pages)
2020-08-11 17:29     ` Joshua M. Clulow
2020-08-12 13:19       ` Steffen Nurpmeso
2020-08-18 16:10         ` Dave Martin
2020-08-11 11:17   ` Dirk Fieldhouse

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=33583fda-da56-7f4c-caa3-08832f654707@gmail.com \
    --to=mtk.lists@gmail.com \
    --cc=austin-group-l@opengroup.org \
    --cc=kre@munnari.oz.au \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=oguzismailuysal@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 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.