Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 9 May 2012 23:05:29 +0400
From: Aleksey Cherepanov <aleksey.4erepanov@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Fwd: bash auto-completion for john

On Wed, May 09, 2012 at 10:52:04PM +0400, Aleksey Cherepanov wrote:
> On Wed, May 09, 2012 at 02:42:48AM +0200, Frank Dittrich wrote:
> > On 05/09/2012 01:15 AM, magnum wrote:
> > > On 05/09/2012 12:31 AM, Frank Dittrich wrote:
> > >> OK. Currently implemented:
> > >>
> > >> 1.
> > >> Improved expansion for --config= (only files *.conf and *.ini will be
> > >> suggested; IMO this is what sane people would want to have, even if you
> > >> could also name your config file john.log)
> > >> Negative side effect: expansion for ~ doesn't work anymore, but that is
> > >> probably less important. (I hate doing this "manually", there really
> > >> must be another way. The code is already full of ugly hacks, no need to
> > >> add even more of them.)
> > > 
> > > Is your very first approach, with "complete -F _filedir_xspec john" not
> > > usable together with auto-completion?
> > 
> > No, because the
> > 	complete -F _filedir_xspec john
> > in my .bashrc would overwrite the
> > 	complete -F _john john
> > at the end of the bash completion script.
> 
> Did you look inside _filedir_xspec? Could you call this function for
> expansion or use similar approach?

Sorry, I already found the answer in this thread that I did not read fully
before posting...

Regards,
Aleksey Cherepanov

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.