Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "Vladimir Prus" <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Improve "help all"
Date: Tue, 31 Oct 2006 12:30:00 -0000	[thread overview]
Message-ID: <13003.192.87.1.22.1162297781.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <ei7eff$al3$1@sea.gmane.org>

>  Daniel Jacobowitz wrote:
>
> > On Sat, Oct 28, 2006 at 02:26:19PM +0200, Eli Zaretskii wrote:
> >> > From: Vladimir Prus <vladimir@codesourcery.com>
> >> > Date: Sat, 28 Oct 2006 15:57:57 +0400
> >> > Cc: gdb-patches@sources.redhat.com
> >> >
> >> > Archived output is attached.
> >>
> >> Thanks.  It looks fine to me.
> >>
> >> Perhaps we should assign classes to the 3 unclassified commands that
> >> appear near the end.  I think they all should go where `set' is, since
> >> that's where their corresponding `set' commands are.
> >
> > Perhaps a strategic assertion when adding commands?
> >
> > Here's a couple of other things we noticed during the discussion that
> > prompted this patch - lesser improvements than mentioning "apropos"
> > prominently, I think:
> >
> >   - 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.  The extra lines convey almost no useful
information to me, and just clutter up my display.

Mark


  reply	other threads:[~2006-10-31 12:30 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 [this message]
2006-10-31 22:28             ` Eli Zaretskii
2006-11-01  9:51               ` Vladimir Prus
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=13003.192.87.1.22.1162297781.squirrel@webmail.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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