Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: Improve "help all"
Date: Sat, 28 Oct 2006 15:29:00 -0000	[thread overview]
Message-ID: <20061028152928.GA396@nevyn.them.org> (raw)
In-Reply-To: <ud58ctyms.fsf@gnu.org>

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.

  - I didn't even know "help all" existed until now.  I couldn't find
    it in the manual, either.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-10-28 15:29 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 [this message]
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
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=20061028152928.GA396@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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