Skip to content
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

bug-fix: set correct bash completion options for fail2ban-regex #1149

Closed

Conversation

pheanex
Copy link
Contributor

@pheanex pheanex commented Aug 2, 2015

fail2ban-regex does not have the same parameters like fail2ban-client or fail2ban-server.
The bash-completion script offered the same options for all of them though.

fail2ban-regex does not have the same parameters like fail2ban-client or fail2ban-server
_init_completion || return
_init_completion || return

if [[ "$1" == *"fail2ban-regex" ]] && [[ "$cur" == "-"* ]];then
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with this change it doesn't suggest any file for the first argument <LOG> and would only complete options (but that also did it before). So what gets fixed really? ;)

PS sorry for the delay

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tbh i don't know anymore (too long ago).
Surely it made sense back then => just close the PR ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants