-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fix Bash completion filename #39
Fix Bash completion filename #39
Conversation
@davidpolverari it's probably not "have to" technically, but the current name is definitely not ideal and if I don't address the QA warning in Gentoo somehow, people will come to me and complain and have a point. |
@davidpolverari PS: in Debian I find the |
Yes, I understand. I'm just trying to understand why the file was named that way in the first place. The examples you picked from Debian show that either bash-completions is too lenient, or those completions don't work. From what I read in bash-completions docs, the file should be named I will just try to figure out why the file was named like that, but the change LGTM. |
@davidpolverari cool! 👍 |
As we are going to create a new dir to host the completions file, why don't we use the dash ( |
ff0a3e0
to
c94b32e
Compare
@davidpolverari I'm leaning towards |
2a935a2
into
resurrecting-open-source-projects:master
In reaction to https://github.com/gentoo/gentoo/blob/2d9d9245cafbbc8ff381f4c0c6509fa8f4c91af9/sys-apps/dcfldd/dcfldd-1.9.2.ebuild#L37-L38
The original QA notice in Gentoo was:
@davidpolverari what do you think?