Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [rfc] Add help text to start-up text
Date: Wed, 12 Jun 2013 22:01:00 -0000	[thread overview]
Message-ID: <51B8D10E.5030409@redhat.com> (raw)

This patch proposes to add a few items to the GDB start-up text to
provide some indication on where the user can find help.

I did not add the wiki and manual URLs to configure et al as I am not
sure that is needed (I guess GDB packagers might have an opinion
here).

Also I am not sure if anything actually parses the initial output of
the GDB start-up text and if adding these lines will affect that.  So
I am seeking comments. 

What do you think?

Cheers

Phil


2013-06-12  Phil Muldoon  <pmuldoon@redhat.com>

	* top.c (print_gdb_version): Add help, apropos description and
	urls to wiki and online documentation.

--

diff --git a/gdb/top.c b/gdb/top.c
index 8ac756f..4c85b51 100644
--- a/gdb/top.c
+++ b/gdb/top.c
@@ -1156,8 +1156,16 @@ Type \"show configuration\" for configuration details.");
     {
       fprintf_filtered (stream,
 			_("\nFor bug reporting instructions, please see:\n"));
-      fprintf_filtered (stream, "%s.", REPORT_BUGS_TO);
+      fprintf_filtered (stream, "%s.\n\n", REPORT_BUGS_TO);
     }
+
+  fprintf_filtered (stream, _("The GDB manual can be found online at:\n\
+<http://www.gnu.org/software/gdb/documentation/>\n"));
+  fprintf_filtered (stream, _("The GDB wiki can be found online at:\n\
+<http://sourceware.org/gdb/wiki/>\n\n"));
+  fprintf_filtered (stream, _("For help, type 'help'.\n"));
+  fprintf_filtered (stream, _("Type 'apropos word' to search for \
+commands related to 'word'.\n"));
 }
 
 /* Print the details of GDB build-time configuration.  */


             reply	other threads:[~2013-06-12 19:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 22:01 Phil Muldoon [this message]
2013-06-13  1:29 ` Sergio Durigan Junior
2013-06-13  9:12 ` Gary Benson
2013-06-13  9:16 ` Pedro Alves
2013-06-21 10:50   ` Phil Muldoon
2013-06-21 15:27     ` Pedro Alves
2013-07-03 12:26       ` Phil Muldoon
2013-07-05  9:36         ` Pedro Alves
2013-07-22 11:50           ` Phil Muldoon

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=51B8D10E.5030409@redhat.com \
    --to=pmuldoon@redhat.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