Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA] Improve help set/unset/show substitute-path
Date: Fri, 12 Jan 2007 07:15:00 -0000	[thread overview]
Message-ID: <20070112071323.GJ537@adacore.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

Hello,

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.

2007-01-12  Joel Brobecker  <brobecker@adacore.com>

        * source.c (_initialize_source): Improve the help text of
        the substitute-path commands.

Tested on x86-linux, no regression.
OK to commit?

Thanks,
-- 
Joel

[-- Attachment #2: help.diff --]
[-- Type: text/plain, Size: 1704 bytes --]

Index: source.c
===================================================================
RCS file: /cvs/src/src/gdb/source.c,v
retrieving revision 1.76
diff -u -p -r1.76 source.c
--- source.c	8 Aug 2006 22:06:06 -0000	1.76
+++ source.c	12 Jan 2007 06:32:06 -0000
@@ -1997,16 +2007,26 @@ Show number of source lines gdb will lis
 
   add_cmd ("substitute-path", class_files, set_substitute_path_command,
            _("\
-Add a source path substitution rule.  If a substitution rule was previously\n\
-set, it is overridden."), &setlist);
+set substitute-path FROM TO\n\
+Add a source path substitution rule replacing FROM into TO in source paths.\n\
+If a substitution rule was previously set for FROM, the old rule is replaced\n\
+by the new one."),
+           &setlist);
 
   add_cmd ("substitute-path", class_files, unset_substitute_path_command,
            _("\
-Remove the current source path substitution rule.  This has no effect\n\
-if no path substitution rule was previously specified."),
+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."),
            &unsetlist);
 
   add_cmd ("substitute-path", class_files, show_substitute_path_command,
-           _("Show the current source path substitution rule."),
+           _("\
+show substitute-path [FROM]\n\
+If a path is specified (FROM), print the source path substitution rule which\n\
+would rewrite that path.\n\
+If no path is specified, print all source path substitution rules."),
            &showlist);
 }

             reply	other threads:[~2007-01-12  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12  7:15 Joel Brobecker [this message]
2007-01-12 14:36 ` Eli Zaretskii
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=20070112071323.GJ537@adacore.com \
    --to=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