-
Notifications
You must be signed in to change notification settings - Fork 68
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
consider whether this could be merged into bash-completion #24
Comments
I'm open to such an idea, too, if the license requirements are satisfied (attribution, disclaimer, etc.). A brief look shows that one uses GPL-2.0 and here it's GPL-3.0. I don't know the exact difference between these two licenses. Maybe they are compatible? There are technical benefits if these two projects are merged. The code could be simpler and maintainers there could help me check if I'm using their code in the best way. The main reason I chose to make it a separate project is to not let experimental code disturb how Finally, I'm sorry I couldn't guarantee long-term maintainership. I made it for fun and threw it out in case it could be helpful to others, too. For this reason, the disclaimer is essential. If they decide to be serious about merging it into a more widely used tool, then they have to understand how it works and be able to fix bugs when they show up in the merged project. So, I guess the best we can do now is to let |
Guess this one here can be closed with your PR? |
Hey there.
Thanks for your nice tool.
It's really something that should be available out-of-the box on every system.
For that reason, would you consider to merge it into bash-completion?
That would have the advantage, that it gets more widespread on readily available (sooner or later) in basically every distribution.
The bash-completion maintainer seemed to be open for such an idea, if you'd continue with the maintenance of the tool there.
Cheers,
Chris.
The text was updated successfully, but these errors were encountered: