From: Benno Schulenberg <bensberg@telfort.nl>
To: util-linux@vger.kernel.org
Subject: [PATCH 02/10] setterm: put an option and its description in a single message
Date: Sat, 15 Feb 2025 17:18:35 +0100 [thread overview]
Message-ID: <20250215161843.12053-2-bensberg@telfort.nl> (raw)
In-Reply-To: <20250215161843.12053-1-bensberg@telfort.nl>
And improve a bit of markup and a wording in the man page.
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
---
term-utils/setterm.1.adoc | 4 ++--
term-utils/setterm.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/term-utils/setterm.1.adoc b/term-utils/setterm.1.adoc
index 38dc81ab5..3fdee3283 100644
--- a/term-utils/setterm.1.adoc
+++ b/term-utils/setterm.1.adoc
@@ -115,14 +115,14 @@ Sets the VESA powerdown interval in minutes. Without an argument, it defaults to
*--powersave* _mode_::
Valid values for _mode_ are:
-*vsync|on*;;
+*vsync*|*on*;;
Puts the monitor into VESA vsync suspend mode.
*hsync*;;
Puts the monitor into VESA hsync suspend mode.
*powerdown*;;
Puts the monitor into VESA powerdown mode.
*off*;;
-Turns monitor VESA powersaving features.
+Turns the monitor's powersaving features off.
*--regtabs*[**=**1-160]::
Clears all tab stops, then sets a regular tab stop pattern, with one tab every specified number of positions. Without an argument, it defaults to *8*. Virtual consoles only.
diff --git a/term-utils/setterm.c b/term-utils/setterm.c
index 53bc6785d..801095c87 100644
--- a/term-utils/setterm.c
+++ b/term-utils/setterm.c
@@ -430,8 +430,8 @@ static void __attribute__((__noreturn__)) usage(void)
fputs(_(" --file <filename> name of the dump file\n"), out);
fputs(USAGE_SEPARATOR, out);
- fputs(_(" --powersave on|vsync|hsync|powerdown|off\n"), out);
- fputs(_(" set vesa powersaving features\n"), out);
+ fputs(_(" --powersave on|vsync|hsync|powerdown|off\n"
+ " set vesa powersaving features\n"), out);
fputs(_(" --powerdown[=<0-60>] set vesa powerdown interval in minutes\n"), out);
fputs(USAGE_SEPARATOR, out);
--
2.48.1
next prev parent reply other threads:[~2025-02-15 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 16:18 [PATCH 01/10] colrm: make the wording of the doc string analogous to that of `col` Benno Schulenberg
2025-02-15 16:18 ` Benno Schulenberg [this message]
2025-02-15 16:18 ` [PATCH 03/10] setterm: mark literal values in the man page in bold Benno Schulenberg
2025-02-15 16:18 ` [PATCH 04/10] textual: fix three misspellings of "unsupported" Benno Schulenberg
2025-02-15 16:18 ` [PATCH 05/10] script: mention in usage that value for <size> may have a suffix Benno Schulenberg
2025-02-15 16:18 ` [PATCH 06/10] textual: make two incorrect synopses identical to a better one Benno Schulenberg
2025-02-15 16:18 ` [PATCH 07/10] rev: standardize the usage header, making the synopsis equal to another Benno Schulenberg
2025-02-15 16:18 ` [PATCH 08/10] mkfs.cramfs: in usage text, separate two direct arguments from options Benno Schulenberg
2025-02-15 16:18 ` [PATCH 09/10] prlimit: in man page, mark --resource as placeholder, not literal option Benno Schulenberg
2025-02-15 16:18 ` [PATCH 10/10] unshare: in usage text, reshuffle options into somewhat related groups Benno Schulenberg
2025-02-18 17:14 ` [PATCH 01/10] colrm: make the wording of the doc string analogous to that of `col` 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=20250215161843.12053-2-bensberg@telfort.nl \
--to=bensberg@telfort.nl \
--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