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

Is BASH completion needed and useful? #456

Closed
maximilien opened this issue Oct 18, 2019 · 3 comments · Fixed by #476
Closed

Is BASH completion needed and useful? #456

maximilien opened this issue Oct 18, 2019 · 3 comments · Fixed by #476
Labels
kind/question Issue type question

Comments

@maximilien
Copy link
Contributor

In what area(s)?

completion command

Classifications:

/kind usage

Ask your question here:

We added zsh completion but it was useless so it's removed in #439 and @rhuss raised the question if we should also remove BASH completion since it's not also too useful.

Separating the two concerns with this issue. We can discuss BASH completion's merits or lack of here and allow #439 to be merged independently.

@maximilien
Copy link
Contributor Author

@sixolet any opinion on this?

@rhuss
Copy link
Contributor

rhuss commented Oct 30, 2019

My feeling is, that completion is useful if we would also add context-sensitive information (like completing on actual service/revision names for e.g. kn service describe). The icing on the cake would be to over e.g. tag names for completion when doing a kn service update --traffic <tab>.

Having only the auto-generated completed is a nice add-on if it works (and it doesn't for zsh completion as it breaks when a help message contains a [ because it then generates invalid shell scripts). We could restrict ourselves to bash-completion, but for now, I think the maintenance costs outweigh the benefits.

@navidshaikh
Copy link
Collaborator

We have the spf13/cobra dep update merged with zsh completion fix, I'll add back the zsh completion.

coryrc pushed a commit to coryrc/client that referenced this issue May 14, 2020
Currently performance tests are grouped by directory, which doesn't apply as 'group by directory' is intended for tests named after file names, and this is different from how performance tests are named. Change it to group by target, so that some of the tests can be grouped based on test targets
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Issue type question
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants