From: Florian Weimer <fweimer@redhat.com>
To: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>
Cc: enh <enh@google.com>, Zack Weinberg <zackw@panix.com>,
Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: Pseudoterminal terminology (was Re: Rename "master" branch to "main"?)
Date: Tue, 28 Jul 2020 17:32:55 +0200 [thread overview]
Message-ID: <875za7u02g.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <990ea0cb-1997-9ad4-e0ea-f5ba54e22066@gmail.com> (Michael Kerrisk's message of "Tue, 28 Jul 2020 17:26:05 +0200")
* Michael Kerrisk:
> Those names (parent, child) do seem strange to me. With process
> creation, those terms make a kind of sense.
Not really: it's rare that a subprocess does not exit before the process
that launched it.
> 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"...
Maybe we can use “pseudoterminal device” and “terminal device”?
Thanks,
Florian
next prev parent reply other threads:[~2020-07-28 15:33 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 [this message]
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
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=875za7u02g.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=enh@google.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).