From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Improve help set/unset/show substitute-path
Date: Fri, 12 Jan 2007 14:36:00 -0000 [thread overview]
Message-ID: <uzm8oqpml.fsf@gnu.org> (raw)
In-Reply-To: <20070112071323.GJ537@adacore.com> (message from Joel Brobecker on Fri, 12 Jan 2007 11:13:23 +0400)
> Date: Fri, 12 Jan 2007 11:13:23 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> As promised to Daniel, hopefully the following patch will make the help
> text of the vaious substitute-path commands a bit better. Anyone either
> wanting to refresh his memory about the usage should now be able to
> use the help text for that. It's also easier to use the command without
> having read the documentation.
Thanks!
> +set substitute-path FROM TO\n\
I think it is better to say "Usage: set substitute-path FROM TO".
> +Add a source path substitution rule replacing FROM into TO in source paths.\n\
GNU standards dislike such usage of the word ``path''. We should use
``file name'' instead. (``Path'' is reserved for lists of directories,
such the values of $PATH and $MANPATH environment variables.)
> +unset substitute-path [FROM]\n\
> +If a path is specified (FROM), delete the associated rule from the current\n\
> +list of substitution rules. A warning is emmitted by the debugger if\n\
> +no rule could be found.\n\
> +If no path is specified, then all substitution rules are deleted."),
I suggest to say this instead:
Delete the rule for substituting FROM in source file names. If FROM
is not specified, all substituting rules are deleted.
If the debugger cannot find a rule for FROM, it will display a
warning.
> +show substitute-path [FROM]\n\
> +If a path is specified (FROM), print the source path substitution rule which\n\
Same here.
next prev parent reply other threads:[~2007-01-12 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 7:15 Joel Brobecker
2007-01-12 14:36 ` Eli Zaretskii [this message]
2007-01-13 14:02 ` Joel Brobecker
2007-01-13 14:11 ` Eli Zaretskii
2007-01-15 3:58 ` Joel Brobecker
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=uzm8oqpml.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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