[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP100C962E76F64FCC5389173FDDD0@phx.gbl>
Date: Mon, 23 Jul 2012 09:26:19 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: john.bash_completion: improve comments
On 07/23/2012 03:28 AM, magnum wrote:
> I can't use it in Makefile (it produces an empty string). Try this:
> sed -ri 's#/etc/bash_completion.d#$(BASH_COMPLETION_DIR)#g' Makefile
>
> It will end up copying the file to the root directory. I presume make
> calls the shell as /bin/sh, leading to bash behaving differently.
Too bad. Should we use /etc/bash_completion.d if it exists?
Or just print a message to read the instructions in
run/john.bash_completion?
(I just noticed that the listed preconditions and the installation
instructions in run/john.bash_completion are more detailed and more up
to date than doc/README.bash-completion.)
Frank
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.
