Adding bash completion #86
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#86
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://github.com/urfave/cli/blob/master/docs/v2/manual.md#bash-completion
sudo wget -O /etc/bash_completion.d/tea https://raw.githubusercontent.com/urfave/cli/master/autocomplete/bash_autocomplete && sudo chmod +x /etc/bash_completion.d/tea
rm it from milestone since I think this has to be done by distro-package-maintainers
but we can leave a note in the docs ...
We could have a subcommand to detect and setup the bash-completion.
In my opinion this overloads tea and package maintainer should keep track of this
hmm looks like hugo for examle has something similar:
by the way urfave/cli has a function to generate man page out of the box too
I think this is our responsibility.
Imagine beeing a package maintainer trying to add autocompletion for three different shells with three different ways to do it of which one is a hack, one requires Go code and the other one must be supported by the application. You probably won't do it.
we either add a "contrib" folder who store manual generated fish/bash completion files or generate things for releases with ci