Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [RFA] Make first and last lines of 'command help documentation' consistent.
Date: Thu, 11 Jul 2019 12:22:00 -0000	[thread overview]
Message-ID: <87y314bw0x.fsf@tromey.com> (raw)
In-Reply-To: <1562797898.1521.10.camel@skynet.be> (Philippe Waroquiers's	message of "Thu, 11 Jul 2019 00:31:38 +0200")

>>>>> "Philippe" == Philippe Waroquiers <philippe.waroquiers@skynet.be> writes:

>> I think this can't be an assertion, because user commands could hit it,
>> and that seems too harsh; but could it be a unit test?  That might be
>> better than printing something magic, especially since IIUC the user can
>> end up seeing this stuff.

Philippe> Effectively, the user can end up seeing this, but only if the GDB test
Philippe> was not run and/or was not fixed.

Or if there is any command written in Python or Guile that has a newline
at the end of its help text.  These commands can be supplied any number
of ways.

Tom


  reply	other threads:[~2019-07-11 12:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-16 19:58 Philippe Waroquiers
2019-07-05 20:04 ` PING " Philippe Waroquiers
2019-07-10 17:02 ` Tom Tromey
2019-07-10 22:31   ` Philippe Waroquiers
2019-07-11 12:22     ` Tom Tromey [this message]
2019-07-11 12:53       ` Pedro Alves
2019-07-11 13:12         ` Tom Tromey
2019-07-11 15:49           ` Pedro Alves
2019-07-11 15:51             ` Pedro Alves
2019-07-11 15:58               ` Tom Tromey
2019-07-11 15:44   ` Pedro Alves
2019-07-11 13:49 ` Pedro Alves
2019-07-29 21:27   ` Philippe Waroquiers
2019-07-11 14:18 ` Pedro Alves
2019-07-11 15:39 ` Pedro Alves
2019-07-11 15:43 ` Pedro Alves

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=87y314bw0x.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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