From: Benno Schulenberg <bensberg@justemail.net>
To: "Util-Linux" <util-linux@vger.kernel.org>
Subject: [patch] uniformizing the help text of 'su'
Date: Fri, 26 Apr 2013 20:24:18 +0200 [thread overview]
Message-ID: <1367000658.896.140661223222089.41EAF215@webmail.messagingengine.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 199 bytes --]
Hi,
Attached patch adapts the help text of 'su' to consistently use
angular brackets to mark to-be-filled-in arguments.
Regards,
Benno
--
http://www.fastmail.fm - Same, same, but different...
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-textual-consistent-angular-brackets-and-lowercase-in.patch --]
[-- Type: text/x-patch; name="0001-textual-consistent-angular-brackets-and-lowercase-in.patch", Size: 3218 bytes --]
From 7e86620bb1f02add3be5a04f7b4ae6c168570279 Mon Sep 17 00:00:00 2001
From: Benno Schulenberg <bensberg@justemail.net>
Date: Mon, 22 Apr 2013 10:06:36 +0200
Subject: [PATCH] textual: consistent angular brackets and lowercase in help text of 'su'
Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
---
login-utils/su-common.c | 23 +++++++++++------------
1 files changed, 11 insertions(+), 12 deletions(-)
diff --git a/login-utils/su-common.c b/login-utils/su-common.c
index bd168ce..d1a7339 100644
--- a/login-utils/su-common.c
+++ b/login-utils/su-common.c
@@ -627,24 +627,23 @@ usage (int status)
{
if (su_mode == RUNUSER_MODE) {
fputs(USAGE_HEADER, stdout);
- printf (_(" %s [options] -u <USER> COMMAND\n"), program_invocation_short_name);
- printf (_(" %s [options] [-] [USER [arg]...]\n"), program_invocation_short_name);
+ printf (_(" %s [options] -u <user> <command>\n"), program_invocation_short_name);
+ printf (_(" %s [options] [-] [<user> [<argument>...]]\n"), program_invocation_short_name);
fputs (_("\n"
- "Run COMMAND with the effective <user> id and group id. If -u not\n"
- "given, fallback to su(1) compatible semantic and shell is executed.\n"
+ "Run <command> with the effective user ID and group ID of <user>. If -u is\n"
+ "not given, fall back to su(1)-compatible semantics and execute standard shell.\n"
"The options -l, -c, -f, -s are mutually exclusive to -u.\n"), stdout);
fputs(USAGE_OPTIONS, stdout);
- fputs (_(
- " -u, --user <user> username\n"), stdout);
+ fputs (_(" -u, --user <user> username\n"), stdout);
} else {
fputs(USAGE_HEADER, stdout);
- printf (_(" %s [options] [-] [USER [arg]...]\n"), program_invocation_short_name);
+ printf (_(" %s [options] [-] [<user> [<argument>...]]\n"), program_invocation_short_name);
fputs (_("\n"
- "Change the effective user id and group id to that of USER.\n"
- "A mere - implies -l. If USER not given, assume root.\n"), stdout);
+ "Change the effective user ID and group ID to that of <user>.\n"
+ "A mere - implies -l. If <user> is not given, root is assumed.\n"), stdout);
fputs(USAGE_OPTIONS, stdout);
}
@@ -655,10 +654,10 @@ usage (int status)
fputs (_(" -, -l, --login make the shell a login shell\n"), stdout);
fputs (_(" -c, --command <command> pass a single command to the shell with -c\n"), stdout);
- fputs (_(" --session-command <command> pass a single command to the shell with -c\n"), stdout);
- fputs (_(" and do not create a new session\n"), stdout);
+ fputs (_(" --session-command <command> pass a single command to the shell with -c\n"
+ " and do not create a new session\n"), stdout);
fputs (_(" -f, --fast pass -f to the shell (for csh or tcsh)\n"), stdout);
- fputs (_(" -s, --shell <shell> run shell if /etc/shells allows it\n"), stdout);
+ fputs (_(" -s, --shell <shell> run <shell> if /etc/shells allows it\n"), stdout);
fputs(USAGE_SEPARATOR, stdout);
fputs(USAGE_HELP, stdout);
--
1.7.0.4
next reply other threads:[~2013-04-26 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 18:24 Benno Schulenberg [this message]
2013-05-06 15:42 ` [patch] uniformizing the help text of 'su' 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=1367000658.896.140661223222089.41EAF215@webmail.messagingengine.com \
--to=bensberg@justemail.net \
--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