From: Phil Muldoon <pmuldoon@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: Patch: Implement Info Command
Date: Thu, 20 Dec 2007 14:31:00 -0000 [thread overview]
Message-ID: <476A7CC4.5090402@redhat.com> (raw)
In-Reply-To: <476A781F.2080707@redhat.com>
Andrew Cagney wrote:
> Phil Muldoon wrote:
>>
>> Usage: info help <sub-command> - will print out the sub-command's
>> help. E.g. info help regs
> this comes across as confusing - shouldn't it print information on the
> help system? Instead:
>
> (fhpd) help info sub-command
>
> Andrew
>
That would require the TopLevelCommand help inner-class system to know
that the command info had help for the sub-command which it doesn't. In
short, without a refactor of how help works, I do not think what you
want will work. At least I think, the way help works is very confusing.
Regards
Phil
next prev parent reply other threads:[~2007-12-20 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 10:57 Phil Muldoon
2007-12-20 11:29 ` Phil Muldoon
2007-12-20 14:12 ` Andrew Cagney
2007-12-20 14:31 ` Phil Muldoon [this message]
2007-12-20 14:35 ` Phil Muldoon
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=476A7CC4.5090402@redhat.com \
--to=pmuldoon@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).