From: Jim Blandy <jimb@redhat.com>
To: rda@sources.redhat.com
Subject: RFA: clean up usage messages
Date: Tue, 19 Oct 2004 19:40:00 -0000 [thread overview]
Message-ID: <vt2d5zelcqp.fsf@zenia.home> (raw)
If you invoke RDA via a long path, the usage message is pretty illegible.
2004-10-12 Jim Blandy <jimb@redhat.com>
* server.c (usage): Don't include the entire pathname in the usage
message.
Index: rda/unix/server.c
===================================================================
RCS file: /cvs/src/src/rda/unix/server.c,v
retrieving revision 1.8
diff -c -r1.8 server.c
*** rda/unix/server.c 7 Oct 2004 19:14:49 -0000 1.8
--- rda/unix/server.c 12 Oct 2004 23:17:56 -0000
***************
*** 250,255 ****
--- 250,259 ----
static void
usage (char *progname)
{
+ /* Remove any leading slashes from the executable name. */
+ if (strrchr (progname, '/'))
+ progname = strrchr (progname, '/') + 1;
+
fprintf (stderr,
"Usage: %s [-v] tcp-port-num executable-file [arguments ...]\n"
" or: %s -a [-v] tcp-port-num process-id\n"
next reply other threads:[~2004-10-19 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 19:40 Jim Blandy [this message]
2004-10-20 15:41 ` Kevin Buettner
2004-10-20 19:20 ` Jim Blandy
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=vt2d5zelcqp.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=rda@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).