This is the mail archive of the
frysk@sourceware.org
mailing list for the frysk project.
Re: info -help expectations?
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: Andrew Cagney <cagney at redhat dot com>
- Cc: frysk <frysk at sources dot redhat dot com>
- Date: Thu, 20 Dec 2007 14:34:43 +0000
- Subject: Re: info -help expectations?
- References: <476A3457.4080405@redhat.com> <476A773A.7010000@redhat.com>
Andrew Cagney wrote:
Phil Muldoon wrote:
I have the info command more or less working so:
(fhpd) info
auxv - Print process auxiliary
debuginfo - Displays debuginfo install paths of a process.
maps - Print process maps
regs - print registers
Hmm; should this print an error (missing command) or the list, and
-help print the list?
I think typing info and no command, it should automatically print the
info help - it is a more friendly touch. All fodder for discussion
though, in the next workflow meeting in the new year.
Since there's an info command what were <<regs vector>> et.al. can
probably be made <<info vector>> et.al.
and
info <subcommand>
and completion?
(fhpd) info <tab>
auxv debuginfo help
maps regs
works as it should. But MultiLevelCommand interprets:
(fhpd) info -help
Error: Unknown command: -help
nice edge case; does the converse <<help info>> work? Like "run", the
class probably needs an explicit check for -help; option parsing would
be overkill.
(fhpd) help info
auxv - Print process auxiliary
debuginfo - Displays debuginfo install paths of a process.
help - Display this help message.
maps - Print process maps
regs - print registers