bash-completion: cleanup and start introducing local uenv labels completion #130
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DISCLAIMER: I'm not very proficient with bash, and it's my first time dealing with CLI11 and bash completion. Any suggestion is welcome! I opted for opening this PR as draft to start sharing a working (and hopefully evolving) experiment and get some early feedback on this.
I started this as an experiment (over #128 which immediately proved to be useful) to explore how bash completion can be extended for
uenv, in particular targeting auto-completion for uenv images available locally (i.e. start and run).Completion is a broad and complicated feature, and I'd like to keep this PR focused on "uenv labels completion for locally available images" as much as possible, while dealing with other extensions separately. However, current design is quite basic and some auxiliary reworkings might be needed to make this work.
TODO
image ls {uenv}is different fromstart {uenv}image ls %ARCH?