Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Fri, 1 Jun 2012 21:33:11 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Fwd: bash auto-completion for john

On 05/31/2012 02:13 AM, magnum wrote:
> I have a hard time re-programming my muscle-memory. Would it be tricky
> to support a colon as an alternative for the equal-sign?

My local version of the bash completion script now "improved" support
for -opt:val.

This requires removing the colon from COMP_WORDBREAKS.
If COMP_WORDBRREAKS contains a colon, the behavior of bash completion
for john remains unchanged.

To remove the colon from COMP_WORDBREAKS, , you can add this line to
your ~./bashrc:

export COMP_WORDBREAKS="${COMP_WORDBREAKS//:}"


For additional information, see comments for __ltrim_colon_completions()
in /etc/bash_completion.

Also, check:
http://www.google.com/search?as_q=COMP_WORDBREAKS+colon


After
$ export COMP_WORDBREAKS="${COMP_WORDBREAKS//:}"
bash completion for john works like this:

$ ./john -fo:d[tab]
becomes
$ ./john -fo=d

And then, the usual completion for -opt=val kicks in.

Of course, this also works with --option: (no value), e.g.:
$ ./john --rules:[tab]
becomes
$ ./john --rules=

So, instead of typing '=' instead of ':', you'd have to hit the [tab]
key one more time.
Does this help?

Frank

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ