All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] cc_t.3type, speed_t.3type, tcflag_t.3type: document all together
Date: Tue, 30 Aug 2022 00:16:58 +0200	[thread overview]
Message-ID: <3cbbf2e5-6213-198f-4cab-c6f42204d471@gmail.com> (raw)
In-Reply-To: <ad1134a85b71db33671385502931aa61029ffc44.1661809591.git.nabijaczleweli@nabijaczleweli.xyz>


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

Hi наб, Branden,

On 8/29/22 23:46, наб wrote:
> speed_t and tcflag_t were both unmentioned in general
> 
> Issue 7 has this to say:
>    The <termios.h> header shall define the following data types through typedef:
>      cc_t     Used for terminal special characters.
>      speed_t  Used for terminal baud rates.
>      tcflag_t Used for terminal modes.
>    The above types shall be all unsigned integer types.
> ---
>   man3type/cc_t.3type     | 14 +++++++++++---
>   man3type/speed_t.3type  |  1 +
>   man3type/tcflag_t.3type |  1 +
>   3 files changed, 13 insertions(+), 3 deletions(-)
>   create mode 100644 man3type/speed_t.3type
>   create mode 100644 man3type/tcflag_t.3type
> 
> diff --git a/man3type/cc_t.3type b/man3type/cc_t.3type
> index 029cf945c..0afdd2cd0 100644
> --- a/man3type/cc_t.3type
> +++ b/man3type/cc_t.3type
> @@ -6,7 +6,7 @@
>   .\"
>   .TH CC_T 3type 2021-11-02 "Linux man-pages (unreleased)"
>   .SH NAME
> -cc_t \- terminal special characters
> +cc_t, speed_t, tcflag_t \- terminal special characters, baud rates, modes
>   .SH LIBRARY
>   Standard C library
>   .RI ( libc )
> @@ -15,10 +15,18 @@ Standard C library
>   .B #include <termios.h>
>   .PP
>   .BR typedef " /* ... */ " cc_t;
> +.BR typedef " /* ... */ " speed_t;
> +.BR typedef " /* ... */ " tcflag_t;
>   .fi
>   .SH DESCRIPTION
> -Used for terminal special characters.
> -It is an unsigned integer type.
> +.B cc_t

Types are formatted with .I, but that seems to be existing practice and 
I don't find it documented anywhere.  (Branden, do you know of any 
source that discusses this?  Is it also like that in other manual pages? 
  Would you do that even if it is the main subject of the page?)



> +is used for terminal special characters,
> +.B speed_t
> +\(em baud rates, and

I would use a 'for' here:
A is used for X, B for Y, and C for Z.
rather than
A is used for X, B -- Y, and C--Z.

Best,

Alex


> +.B tcflag_t
> +\(em modes.
> +.PP
> +All are unsigned integer types.
>   .SH STANDARDS
>   POSIX.1-2001 and later.
>   .SH SEE ALSO
> diff --git a/man3type/speed_t.3type b/man3type/speed_t.3type
> new file mode 100644
> index 000000000..26cfd0171
> --- /dev/null
> +++ b/man3type/speed_t.3type
> @@ -0,0 +1 @@
> +.so man3type/cc_t.3type
> diff --git a/man3type/tcflag_t.3type b/man3type/tcflag_t.3type
> new file mode 100644
> index 000000000..26cfd0171
> --- /dev/null
> +++ b/man3type/tcflag_t.3type
> @@ -0,0 +1 @@
> +.so man3type/cc_t.3type

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

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

  parent reply	other threads:[~2022-08-29 22:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 21:46 [PATCH 1/2] cc_t.3type, speed_t.3type, tcflag_t.3type: document all together наб
2022-08-29 21:46 ` [PATCH 2/2] termios.3: mention the integer types in SEE ALSO наб
2022-08-29 22:16 ` Alejandro Colomar [this message]
2022-08-29 22:33   ` [PATCH 1/2] cc_t.3type, speed_t.3type, tcflag_t.3type: document all together наб
2022-08-29 22:36     ` Alejandro Colomar
2022-08-29 22:48       ` наб
2022-08-29 22:54         ` 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=3cbbf2e5-6213-198f-4cab-c6f42204d471@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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.