From: Joe Jin <joe.jin@oracle.com>
To: Benno Schulenberg <bensberg@telfort.nl>, util-linux@vger.kernel.org
Cc: Zhenwei Pi <pizhenwei@bytedance.com>
Subject: Re: [PATCH 05/10] irqtop: improve several more option descriptions, and align them all
Date: Mon, 31 Mar 2025 09:12:41 -0700 [thread overview]
Message-ID: <e45f45de-62f4-4263-ab71-828780e878bd@oracle.com> (raw)
In-Reply-To: <7c31b1e6-1510-4066-a565-2d8343b99b36@telfort.nl>
On 3/31/25 08:47, Benno Schulenberg wrote:
>
> Op 31-03-2025 om 17:02 schreef Joe Jin:
>> On 3/31/25 02:44, Benno Schulenberg wrote:
>>> fputs(_("\nThe following interactive key commands are valid:\n"), stdout);
>>> fputs(_(" i sort by IRQ\n"), stdout);
>>> fputs(_(" t sort by TOTAL\n"), stdout);
>>> fputs(_(" d sort by DELTA\n"), stdout);
>>> fputs(_(" n sort by NAME\n"), stdout);
>>> - fputs(_(" q Q quit program\n"), stdout);
>>> + fputs(_(" q quit program\n"), stdout);
>>
>> Why remove the "Q"?
>
> It looks ugly. And why would the user want to hold Shift before pressing q,
> when just pressing q will do? Holding Shift has no extra effect.
Then should it be removed from parse_input() as well?
Thanks,
Joe
>
> If the user has CapsLock activated, they will simply press the q key, and
> expect it to work -- and it will work, like they know from other tools.
> No need to explicitly mention this, because it makes it seem as if it is
> something special.
>
>
> Benno
>
next prev parent reply other threads:[~2025-03-31 16:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 9:44 [PATCH 01/10] enosys: add the missing arguments of -s and -i to the usage text Benno Schulenberg
2025-03-31 9:44 ` [PATCH 02/10] uclampset: simplify the synopsis in the --help " Benno Schulenberg
2025-03-31 9:44 ` [PATCH 03/10] last: don't use a tab character " Benno Schulenberg
2025-03-31 9:44 ` [PATCH 04/10] irqtop: improve the description of --batch, and align it with others Benno Schulenberg
2025-03-31 14:57 ` Joe Jin
2025-03-31 9:44 ` [PATCH 05/10] irqtop: improve several more option descriptions, and align them all Benno Schulenberg
2025-03-31 15:02 ` Joe Jin
2025-03-31 15:47 ` Benno Schulenberg
2025-03-31 16:12 ` Joe Jin [this message]
2025-04-01 9:17 ` Benno Schulenberg
2025-04-02 10:58 ` Karel Zak
2025-03-31 9:44 ` [PATCH 06/10] findmnt: (man) remove duplicated option, and correct a description Benno Schulenberg
2025-03-31 9:44 ` [PATCH 07/10] hardlink: fix typoed semicolon to colon in error message Benno Schulenberg
2025-03-31 9:44 ` [PATCH 08/10] lsblk: (man) remove the incorrect spaces between the arguments of --ct Benno Schulenberg
2025-03-31 9:44 ` [PATCH 09/10] coresched: reduce excessive whitespace and verbosity in usage text Benno Schulenberg
2025-03-31 11:00 ` Phil Auld
2025-04-03 8:11 ` Karel Zak
2025-04-03 9:55 ` Benno Schulenberg
2025-04-03 12:08 ` Karel Zak
2025-03-31 9:44 ` [PATCH 10/10] coresched: rename option '--dest-type' to just '--type' Benno Schulenberg
2025-03-31 11:09 ` Phil Auld
2025-04-01 8:35 ` Karel Zak
2025-04-01 9:25 ` Benno Schulenberg
2025-04-01 12:20 ` Karel Zak
2025-04-02 11:11 ` [PATCH 01/10] enosys: add the missing arguments of -s and -i to the usage text Karel Zak
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=e45f45de-62f4-4263-ab71-828780e878bd@oracle.com \
--to=joe.jin@oracle.com \
--cc=bensberg@telfort.nl \
--cc=pizhenwei@bytedance.com \
--cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).