Open marcandrebenoit opened 2 months ago
@marcandrebenoit
Yes, you're absolutely right—at the moment, users need to manually save the output to a completions directory, such as /etc/bash_completion.d
, for it to work properly. Updating the documentation with clearer instructions sounds like a great idea, and I really appreciate your suggestion.
If you're interested, feel free to open a Pull Request with the improvement—contributions are always welcome!
Question
After running the command, I don't see the output appended in my .bashrc and I see no clear instructions in the code output on what to do next.
Does the command also outputs in a new or existing file in path? Do I need to manually copy the output and append it in .bashrc (and log back in) for the completions to work ?
I'd suggest to add some context instructions in code comments and/or in the wiki regarding this if that's the case.
Environment