All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: lvm-devel@redhat.com
Subject: revised error output: Run ... --help for more information
Date: Fri, 21 Sep 2007 13:58:35 +0200	[thread overview]
Message-ID: <87vea4dyc4.fsf@rho.meyering.net> (raw)
In-Reply-To: <20070921115330.GX18444@agk.fab.redhat.com> (Alasdair G. Kergon's message of "Fri, 21 Sep 2007 12:53:30 +0100")

Alasdair G Kergon <agk@redhat.com> wrote:
> On Fri, Sep 21, 2007 at 01:30:03PM +0200, Jim Meyering wrote:
>>     $ ./lvchange
>>       Need 1 or more of -a, -C, -j, -m, -M, -p, -r, --resync, --refresh, --alloc, --addtag, --deltag or --monitor
>>       lvchange: Run `lvchange --help' for more information.
>
> So we should certainly drop the 'lvchange:' now from the second line of output.

Good.  It's already gone in my current sources.

>>       lvchange: Need 1 or more of -a, -C, -j, -m, -M, -p, -r, --resync, --refresh, --alloc, --addtag, --deltag or --monitor
>
> So should we add a new option (command_names = 2, perhaps)
> that only applies it to messages produced using log_error()
> rather than for all output?  [And make this the default setting.]
>
> Or do we only want it (roughly speaking) for EINVALID_CMD_LINE not for
> ECMD_FAILED?

Personally, I'd like the "command_name: " prefix
on all "real" diagnostic lines -- and that'd be consistent
with what other tools do.  In my experience, the "Run ... --help"
diagnostic is most useful on EINVALID_CMD_LINE failures.



      reply	other threads:[~2007-09-21 11:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17 12:55 proposed change: don't spew all --help output for every usage error Jim Meyering
2007-09-17 19:09 ` Alasdair G Kergon
2007-09-21 11:30   ` revised error output: Run ... --help for more information Jim Meyering
2007-09-21 11:43     ` Alasdair G Kergon
2007-09-21 11:49       ` Jim Meyering
2007-09-21 11:53     ` Alasdair G Kergon
2007-09-21 11:58       ` Jim Meyering [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:
  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=87vea4dyc4.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=lvm-devel@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.