Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@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:12:00 -0000	[thread overview]
Message-ID: <20130613082003.GA4510@blade.nx> (raw)
In-Reply-To: <51B8D10E.5030409@redhat.com>

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.

Great!

> 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).

I think they're good how they are.  I can see the utility of changing
the bug-reporting URL, but not the others.  It might be useful to lift
them out of the translated string, but that's just idle speculation on
my part :)

> 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. 

I really hope things aren't parsing this!

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

The quotes here should be \", to match those above.

Cheers,
Gary

-- 
http://gbenson.net/


  parent reply	other threads:[~2013-06-13  8:20 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 [this message]
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=20130613082003.GA4510@blade.nx \
    --to=gbenson@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