Closed marchersimon closed 1 week ago
Is there a reason this hasn't been done yet?
Because the only way to do that is to utilize a post-install script which is considered a kinda grey zone territory. Some folks explicitly prevent those from running using either npm config or the corresponding installation-time CLI option.
As I mentioned here https://github.com/tldr-pages/tldr-node-client/issues/311#issuecomment-790728537 cleaner way would be to implement completion
subcommand like:
tldr completion bash
# or
tldr completion zsh
which would then output the completion code for the requested shell. That way users can either add it to their profile or write to completion dirs you already listed. And they would have to do that manually as opposed to running stuff behind their back.
I agree @vladimyr, a subcommand would probably be the best option and is also pretty common. 👍🏻
The completion files at bin/completion for
bash
andzsh
currently aren't copied anywhere, so they cannot be seen bybash
orzsh
.For
bash
completion files have to go to/usr/share/bash-completion/completions/
.For
zsh
completion files have to be in any directory in$fpath
(e.g./usr/share/zsh/functions/Completion/Zsh/
).Is there a reason this hasn't been done yet?