From: Jared Finder <jared@finder.org>
To: "Günther Noack" <gnoack3000@gmail.com>
Cc: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Subject: Re: [PATCH man v2 1/2] TIOCLINUX.2const: Restructure documentation for TIOCL_SETSEL selection modes
Date: Sun, 23 Feb 2025 15:13:35 -0800 [thread overview]
Message-ID: <1094ef00ff08bbede90c01f7a36df293@finder.org> (raw)
In-Reply-To: <20250223213642.10042-2-gnoack3000@gmail.com>
I'm not a regular kernel developer, so feel free to ignore my
recommendations if they are not aligned with the level of documentation
usually provided.
On 2025-02-23 13:36, Günther Noack wrote:
> * Indent the documented selection modes into tagged paragraphs.
> * Document constants from the header file (tiocl.h) instead of numbers.
>
> Signed-off-by: Günther Noack <gnoack3000@gmail.com>
> ---
> man/man2const/TIOCLINUX.2const | 23 ++++++++++++++++++-----
> 1 file changed, 18 insertions(+), 5 deletions(-)
>
> diff --git a/man/man2const/TIOCLINUX.2const
> b/man/man2const/TIOCLINUX.2const
> index c0acdd0ea..5db3f6ea6 100644
> --- a/man/man2const/TIOCLINUX.2const
> +++ b/man/man2const/TIOCLINUX.2const
> @@ -65,11 +65,24 @@ are the ending
> column and row.
> (Upper left corner is row=column=1.)
> .I sel_mode
> -is 0 for character-by-character selection,
> -1 for word-by-word selection,
> -or 2 for line-by-line selection.
> -The indicated screen characters are highlighted and saved
> -in a kernel buffer.
> +may be one of the following operations:
> +.RS
> +.TP
> +.B TIOCL_SELCHAR
> +Select character-by-character.
> +The indicated screen characters are highlighted
> +and saved in a kernel buffer.
I would recommend also saying
> +.TP
> +.B TIOCL_SELWORD
> +Select word-by-word.
> +The indicated screen characters are highlighted
> +and saved in a kernel buffer.
I would recommend also saying something like "The start is expanded
backward and the end is expanded forwards to select entire words."
> +.TP
> +.B TIOCL_SELLINE
> +Select line-by-line.
> +The indicated screen characters are highlighted
> +and saved in a kernel buffer.
> +.RE
Similarly, mention how the start / end is expanded here too.
> .IP
> Since Linux 6.7, using this subcode requires the
> .B CAP_SYS_ADMIN
-- MJF
next prev parent reply other threads:[~2025-02-23 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-23 21:36 [PATCH man v2 0/2] TIOCLINUX.2const: Document TIOCL_SETSEL selection modes Günther Noack
2025-02-23 21:36 ` [PATCH man v2 1/2] TIOCLINUX.2const: Restructure documentation for " Günther Noack
2025-02-23 23:13 ` Jared Finder [this message]
2025-03-02 7:06 ` Alejandro Colomar
2025-03-02 19:45 ` Günther Noack
2025-03-02 19:00 ` Günther Noack
2025-02-23 21:36 ` [PATCH man v2 2/2] TIOCLINUX.2const: Document missing " Günther Noack
2025-02-23 23:19 ` Jared Finder
2025-03-02 19:23 ` Günther Noack
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=1094ef00ff08bbede90c01f7a36df293@finder.org \
--to=jared@finder.org \
--cc=alx@kernel.org \
--cc=gnoack3000@gmail.com \
--cc=linux-man@vger.kernel.org \
/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