[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bfb4877e55f5a4b5e5fb9c7ddde71e2a@smtp.hushmail.com>
Date: Tue, 05 Jun 2012 09:53:36 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Do we need --list=formats?
On 06/05/2012 09:21 AM, magnum wrote:
> On 06/05/2012 08:29 AM, Frank Dittrich wrote:
>> While we are at it:
>> Should we also add a --list=subformats, which does the same as
>> --subformat=LIST, except that it writes to stdout instead of stderr?
>
> This is trivial, and dynamic_DISPLAY_ALL_FORMATS() already writes to
> stdout.
>
>> Then we could discourage the use of --subformat=LIST.
>> (My bash completion script could even try to replace --subformat with
>> --list=subformats.)
>> And in the next release we just get rid of --subformats?
>
> Yes. We could pull it from the usage blob immediately and drop the
> support later. We might add --list to the usage instead, with a
> description like:
>
> --list=WHAT List capabilities, see doc/OPTIONS or --list=?
Done. BTW the bash completion doesn't seem to complete further than
--list= right now, I think it did earlier?
magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
