This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Improve "help all"
> 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