Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [rfc] Add help text to start-up text
Date: Thu, 13 Jun 2013 09:16:00 -0000	[thread overview]
Message-ID: <51B98CEE.3080006@redhat.com> (raw)
In-Reply-To: <51B8D10E.5030409@redhat.com>

On 06/12/2013 08:50 PM, Phil Muldoon wrote:
> 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?

I think at least the help and apropos bits are going to be super useful.
I like that a lot.

> +  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"));

IMO, putting only one url here would be enough, and would make this
more condensed.  I don't think users need to care about the fact that
some documentation is in a wiki.  We should add a link
to the wiki to <http://www.gnu.org/software/gdb/documentation/>.  There's
more than the manual there even.
We could then just say something like:

(I suggest the imperative, like the help/apropos sentences, which turns
out shorter too.)

"Find the GDB manual and other documentation resources online at:\n\
<http://www.gnu.org/software/gdb/documentation/\n"

The url we hardcode in GDB stays there forever (as in, people will
use the first gdb release that includes it for many years), so having
a single point of entry is more flexible.

> +  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.  */

-- 
Pedro Alves


  parent reply	other threads:[~2013-06-13  9:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 22:01 Phil Muldoon
2013-06-13  1:29 ` Sergio Durigan Junior
2013-06-13  9:12 ` Gary Benson
2013-06-13  9:16 ` Pedro Alves [this message]
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=51B98CEE.3080006@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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