public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: enh <enh@google.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Zack Weinberg <zackw@panix.com>,
	"Carlos O'Donell" <carlos@redhat.com>,
	 libc-alpha <libc-alpha@sourceware.org>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
	 Florian Weimer <fweimer@redhat.com>,
	Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: Pseudoterminal terminology (was Re: Rename "master" branch to "main"?)
Date: Tue, 28 Jul 2020 11:47:43 -0700	[thread overview]
Message-ID: <CAJgzZoruApyP_GMJQ-1RUUU_WKGzbXiC9zKsX5n+qiG0Lo2gmQ@mail.gmail.com> (raw)
In-Reply-To: <990ea0cb-1997-9ad4-e0ea-f5ba54e22066@gmail.com>

On Tue, Jul 28, 2020 at 8:26 AM Michael Kerrisk (man-pages) <
mtk.manpages@gmail.com> wrote:

> On 7/27/20 10:52 PM, enh wrote:
>
> [...]
>
> > yeah, i'm can't say i'm particularly excited about those terms ... but
> > "master" and "slave" weren't super obvious either.
> >
> > tbh, i don't think any of the choices in this thread are actually _worse_
> > in terms of clarity (though existing practice was at least consistent so
> > you could rtfm).
> >
> > i found the python reference i failed to find for michael earlier... it
> > looks like i couldn't find it because it's the one master/slave change to
> > python that they didn't actually submit. in
> > https://github.com/python/cpython/pull/9100 they were going to go with
> > parent and child but gvanrossum said they shouldn't change unless Unix
> > changes.
> >
> > at least parent/child are names that most folks (including non-native
> > speakers) will have had to learn already.
>
> Those names (parent, child) do seem strange to me. With process
> creation, those terms make a kind of sense. There's no obvious sense
> to me for parent/child in the pty context. (The nearest I can see: The
> parent device tells the child device what to do? Now that's a whole
> other interesting can of worms.)
>

parent/child might be a good choice for the related forkpty(). (given
bionic's "you'll probably be looking at this in Android Studio or Visual
Studio Code's argument name completion UI, so let's use a longer name to
save you a trip to the man page if you know roughly what you're doing but
can't remember what order the arguments are in" style, that would probably
still be `int forkpty(int* _Nonnull __parent_pty_fd, char* _Nullable
__child_tty_name, ...`.)

(note also that the man page for forkpty() seems to be the only place the
return type is given as pid_t rather than int --- afaict all the libcs
actually use int?)


> > golang went with pty/tty (
> >
> https://github.com/creack/pty/commit/7dc38fb350b1d71383eed149e73acb7bae231ddb
> )
> > which is interestingly simple.
>
> The simplicity of it is appealing. But, how does this read in
> prose documentation. Do we replace actual English words with
> abbreviations ("pty", "tty")? That looks a little weird in writing,
> and seems weirder when spoken aloud. And then: "the pseudoterminal
> pty device" seems a little bit like something I might find in
> "The Department of Redundancy Dept"...
>
> I think proper English nouns would be preferable, if we can find
> ones that are suitable.
>
> Cheers,
>
> Michael
>
>
> --
> Michael Kerrisk
> Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
> Linux/UNIX System Programming Training: http://man7.org/training/
>

  parent reply	other threads:[~2020-07-28 18:47 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 18:10 Rename "master" branch to "main"? Carlos O'Donell
2020-06-30 18:35 ` Paul Eggert
2020-06-30 20:16   ` Carlos O'Donell
2020-06-30 21:08     ` Paul Eggert
2020-06-30 18:59 ` Florian Weimer
2020-06-30 20:14   ` Carlos O'Donell
2020-07-01  9:38     ` Florian Weimer
2020-07-03 15:26   ` Richard Earnshaw
2020-07-03 15:33     ` Carlos O'Donell
2020-06-30 21:24 ` Joseph Myers
2020-06-30 21:44   ` Carlos O'Donell
2020-06-30 22:56     ` Joseph Myers
2020-06-30 22:59 ` DJ Delorie
2020-07-01  7:17   ` Andreas Schwab
2020-07-01 15:42     ` Carlos O'Donell
2020-07-01 12:29   ` Adhemerval Zanella
2020-07-01 12:49     ` Carlos O'Donell
2020-07-01 13:41       ` Adhemerval Zanella
2020-07-01 16:15   ` Carlos O'Donell
2020-07-01 17:45     ` DJ Delorie
2020-07-01 18:29       ` Paul Eggert
2020-07-01 18:43         ` DJ Delorie
2020-07-02 15:40 ` Zack Weinberg
2020-07-02 16:00   ` Florian Weimer
2020-07-02 16:36   ` Joseph Myers
2020-07-02 20:46     ` Paul Eggert
2020-07-04 16:43     ` Zack Weinberg
2020-07-02 20:58   ` Michael Kerrisk
2020-07-03 15:20     ` Carlos O'Donell
2020-07-04 16:52     ` Pseudoterminal terminology (was Re: Rename "master" branch to "main"?) Zack Weinberg
2020-07-05 14:54       ` J William Piggott
2020-07-06  9:18         ` Michael Kerrisk (man-pages)
2020-07-06  9:13       ` Michael Kerrisk (man-pages)
2020-07-27 20:32         ` Michael Kerrisk (man-pages)
2020-07-27 20:52           ` enh
2020-07-27 20:55             ` enh
2020-07-27 20:59               ` Florian Weimer
2020-07-27 22:48                 ` enh
2020-07-28 15:26             ` Michael Kerrisk (man-pages)
2020-07-28 15:32               ` Florian Weimer
2020-07-28 15:44                 ` enh
2020-07-28 19:16                 ` Michael Kerrisk (man-pages)
2020-07-28 19:18                   ` enh
2020-07-28 18:47               ` enh [this message]
2020-07-28 19:27                 ` Michael Kerrisk (man-pages)
2020-07-28 19:33                   ` enh
2020-07-03 15:22 ` Rename "master" branch to "main"? Richard Earnshaw
2020-07-03 15:37   ` Carlos O'Donell
2020-07-13 15:14 ` Carlos O'Donell
2021-01-14  9:21 ` Mike Frysinger
2021-01-14 11:17   ` Siddhesh Poyarekar
2021-01-14 17:54   ` Joseph Myers
2021-01-14 20:56     ` Carlos O'Donell
2021-01-14 21:42       ` Mike Frysinger
2021-01-20 13:49         ` Carlos O'Donell
2021-01-21  0:23           ` Mike Frysinger
2021-01-21 13:30             ` Carlos O'Donell
2021-01-21 13:57               ` Andreas Schwab
2021-01-21 17:06               ` Mike Frysinger
2021-01-21 19:37                 ` Carlos O'Donell
2021-01-21 20:19                   ` Andreas Schwab
2021-01-22  2:32                   ` Mike Frysinger

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=CAJgzZoruApyP_GMJQ-1RUUU_WKGzbXiC9zKsX5n+qiG0Lo2gmQ@mail.gmail.com \
    --to=enh@google.com \
    --cc=carlos@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mtk.manpages@gmail.com \
    --cc=zackw@panix.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 read-only IMAP folder(s) and NNTP newsgroup(s).