public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Benno Schulenberg <bensberg@justemail.net>
To: Sami Kerola <kerolasa@iki.fi>
Cc: "Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: [PATCH 1/4] setterm: add usage() descriptions
Date: Sat, 24 May 2014 14:30:51 +0200	[thread overview]
Message-ID: <1400934651.15812.121082081.6ADC22B3@webmail.messagingengine.com> (raw)
In-Reply-To: <1400929696-12548-2-git-send-email-kerolasa@iki.fi>


Hi Sami,

On Sat, May 24, 2014, at 13:08, Sami Kerola wrote:
> +	fputs(_(" --inversescreen <on|off>          inverse foreground and background colors\n"), out);

s/inverse/swap/
s/colors/colors for the whole screen/

And all these <on|off> should be [on|off], like in the man page,
as they are literal arguments and optional.

> +	fputs(_(" --foreground    <default|color>   set foreground color\n"), out);

default|<color>

> +	fputs(_(" --reverse       <on|off>          reverse all output options\n"), out);

Hm?  Shouldn't that be "set reverse video"?
Or maybe "swap foreground and background colors from here"?
It doesn't invert brightness or other attributes.

> +	fputs(_(" --clear         <all|rest>        clear screen and set cursor position\n"), out);

[all|rest]

> +	fputs(_(" --regtabs       <1-160>           set default tab stop position\n"), out);

To be consistent this should be "--regtabs <number>", and then add that
<number> can be 1..160.  But that loses conciseness.

> +	fputs(_(" --blank         <0-60|force|poke> set inactivity interval\n"), out);

--blank  [<number>|force|poke]
and <number> can be 1..60 (minutes)

Benno

-- 
http://www.fastmail.fm - Send your email first class


  reply	other threads:[~2014-05-24 12:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-24 11:08 [PATCH 0/4] setterm: documentation updates Sami Kerola
2014-05-24 11:08 ` [PATCH 1/4] setterm: add usage() descriptions Sami Kerola
2014-05-24 12:30   ` Benno Schulenberg [this message]
2014-05-25 10:57     ` Sami Kerola
2014-05-25 20:51       ` Benno Schulenberg
2014-05-24 11:08 ` [PATCH 2/4] docs: setterm.1 add missing options to manual page and remove duplicate Sami Kerola
2014-05-24 12:33   ` Benno Schulenberg
2014-05-25 10:57     ` Sami Kerola
2014-05-24 11:08 ` [PATCH 3/4] docs: setterm.1 add options compatibility note Sami Kerola
2014-05-24 12:38   ` Benno Schulenberg
2014-05-25 10:58     ` Sami Kerola
2014-05-24 11:08 ` [PATCH 4/4] docs: setterm.1 clean up manual page groff style Sami Kerola
2014-05-24 12:44   ` Benno Schulenberg
2014-05-25 10:58     ` Sami Kerola
2014-05-25 21:10       ` Benno Schulenberg
2014-05-26  8:42         ` Sami Kerola
2014-05-26 10:11           ` Karel Zak
2014-05-26 15:46             ` Sami Kerola
2014-05-27 14:46               ` Karel Zak
2014-05-29  9:48                 ` Sami Kerola
2014-05-29 10:23                   ` Ruediger Meier
2014-05-30  7:44                     ` Sami Kerola
2014-06-01 22:35                       ` Ruediger Meier
2014-06-02 16:42                         ` Sami Kerola
2014-06-02 21:23                           ` Bernhard Voelker
2014-06-02 21:35                             ` Ruediger Meier

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=1400934651.15812.121082081.6ADC22B3@webmail.messagingengine.com \
    --to=bensberg@justemail.net \
    --cc=kerolasa@iki.fi \
    --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