public inbox for
 help / color / mirror / Atom feed
From: Phil Muldoon <>
To: Andrew Cagney <>
Cc: frysk <>
Subject: Re: info -help expectations?
Date: Thu, 20 Dec 2007 14:34:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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>> can 
> probably be made <<info vector>>
>> 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

      reply	other threads:[~2007-12-20 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20  9:22 Phil Muldoon
2007-12-20 14:08 ` Andrew Cagney
2007-12-20 14:34   ` Phil Muldoon [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).