New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bash completion bug #1066
Comments
What does
If you get |
See also section "Prerequisites" of doc/README.bash-completion:
|
May be I should add a comment similar to the one in john.bash_completion's lines 12-20 closer to the source code lines which cause the problems when extended pattern matching is disabled, i.e., line 565. |
Extended patterns are turned on, AND I am running 4.3.11(1) bash (with the recent patches).
|
The only explanation is that
immediately before
into your ~/.bashrc file? I have
in my ~/.bashrc now, and I get
when I start a new shell or xterm. |
I just tested this with ubuntu 14.10. Adding
at the end of my /home/fd/.bashrc file works for me. |
I get a very similar error on Super. It has bash 4.1.2
|
I tried enbling extglob on Super and then source JtR bash completion.
|
looks like bash completion is not installed on super. |
On well it should work. |
I put the load line at the bottom of the .bashrc and it is working fine. Gonna mark this as PEBCAK and close it. |
When I start my bash shell, I get this:
ubuntu-64 in a VM. To install jtr bash completion, I simply added
. /JtR/bleed/run/john.bash_completion
to my ~/.bashrc fileThe text was updated successfully, but these errors were encountered: