-
Notifications
You must be signed in to change notification settings - Fork 192
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 #417
bash completion #417
Conversation
Nice! When I was testing CLI from your previous PR, I was thinking "it would be really nice to have completion for this tool, at least for D-Bus paths" :D And you've actually made it! PS. |
This script is not quite perfect - ALSA device names can contain spaces, and this expansion on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's hard for me to review it properly, because I'm not a wizard-level basher... I hope you will understand that :D
Co-authored-by: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
While merging into master, I've changed script location from |
A bash completion script for the bluez-alsa programs. This makes bluealsa-cli and bluealsa-rfcomm in particular much easier to use as it saves having to type out object paths.
I also found a couple of typos in the man pages while working n this, so there is also a commit for that too.