Completion and usage message output should use name of invoked command, not "hassio-cli" #140
Labels
Comments
mjrider
added a commit
to mjrider/hassio-cli
that referenced
this issue
Jan 15, 2019
This fixes home-assistant#140 by looking at the name of the binary used to invoke the cli. as side effect, the completion and help contain the whatever used to invoke the binary, using go run for example with use the name `main`
mjrider
added a commit
to mjrider/hassio-cli
that referenced
this issue
Jan 15, 2019
This fixes home-assistant#140 by looking at the name of the binary used to invoke the cli. as side effect, the completion and help contain the whatever used to invoke the binary, using go run for example with use the name `main`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed in #138, when one issues the completion command to output bash completion, the output is always applied to the command name
hassio-cli. This is a problem if the command is installed under a different name, e.g.hassio.The same problem seems to be in a lot of other places as well, for example usage messages say
hassio-clino matter what the executable's filename is.The fix would be to use the invoked command's name in usage messages and bash completion output etc.
The text was updated successfully, but these errors were encountered: