From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: Improve "help all"
Date: Wed, 01 Nov 2006 09:51:00 -0000 [thread overview]
Message-ID: <ei9qlv$olr$1@sea.gmane.org> (raw)
In-Reply-To: <u64e06ry2.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Tue, 31 Oct 2006 13:29:41 +0100 (CET)
>> From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
>> Cc: gdb-patches@sources.redhat.com
>> > >
>> > > - The help output doesn't mention which class a command is in; this
>> > > might be useful, for finding related commands.
>> >
>> >
>> > The attached patch implements it. The output I get is:
>> >
>> > (gdb) help step
>> > Step program until it reaches a different source line.
>> > Argument N means do this N times (or till program stops for another
>> > reason).
>> >
>> > Run "help running" for the list of all commands in this class.
>> >
>> > This patch would require changing "breakpoint" command that already
>> > suggests
>> > to use "help breakpoints" in its own help string -- I'll do this later
>> > if this patch is approved.
>>
>> I really don't like this.
>
> Me neither. How about this output instead:
>
> (gdb) help step
> Step program until it reaches a different source line.
> Argument N means do this N times (or till program stops for another
> reason).
> (This command belongs to the class `running'.)
So:
- you changed wording (and I trust you on this)
- you remove a newline.
I'm not sure I understand the motivation for lumping everything in one text
block, for the sake of saving a single line. But if that's the general
agreement, I can change the patch to produce the above output?
Will it be OK then?
- Volodya
next prev parent reply other threads:[~2006-11-01 9:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 19:40 Vladimir Prus
2006-10-28 11:29 ` Eli Zaretskii
2006-10-28 11:58 ` Vladimir Prus
2006-10-28 12:26 ` Eli Zaretskii
2006-10-28 15:29 ` Daniel Jacobowitz
2006-10-28 18:57 ` Eli Zaretskii
2006-10-31 12:11 ` Vladimir Prus
2006-10-31 12:30 ` Mark Kettenis
2006-10-31 22:28 ` Eli Zaretskii
2006-11-01 9:51 ` Vladimir Prus [this message]
2006-11-01 20:16 ` Eli Zaretskii
2006-11-01 22:50 ` Mark Kettenis
2006-11-02 4:19 ` Eli Zaretskii
2006-10-31 12:15 ` Vladimir Prus
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='ei9qlv$olr$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb-patches@sources.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