Skip to content

Commit 15da826

Browse files
RobertKieltyzkat
authored andcommitted
docs: bash_completion.d dir found in /etc not /usr/local (#72)
I found this page useful for setting up npm command completion. Thank you npm documentation team. This suggested changed is based on my system which runs Ubuntu where the completion directory path for bash is found in /etc/bash_completion.d and not /usr/local/etc/bash_completion.d I dug around docs for this in The Bash Manual https://www.gnu.org/software/bash/manual/bashref.html#Programmable-Completion and on some an old (sadly retired) Debian Admin Site https://debian-administration.org/article/317/An_introduction_to_bash_completion_part_2 which seemed supportive of the dir being in /etc but I do not have access to an OS X machine where I guess bash_completion.d could be in /usr/local/etc so I left it in. PR-URL: #72 Credit: @RobertKielty Reviewed-By: @zkat
1 parent 27217da commit 15da826

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

doc/cli/npm-completion.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,10 @@ everywhere:
1717
npm completion >> ~/.bashrc
1818
npm completion >> ~/.zshrc
1919

20-
You may of course also pipe the output of npm completion to a file
21-
such as `/usr/local/etc/bash_completion.d/npm` if you have a system
22-
that will read that file for you.
20+
You may of course also pipe the output of `npm completion` to a file
21+
such as `/usr/local/etc/bash_completion.d/npm` or
22+
`/etc/bash_completion.d/npm` if you have a system that will read
23+
that file for you.
2324

2425
When `COMP_CWORD`, `COMP_LINE`, and `COMP_POINT` are defined in the
2526
environment, `npm completion` acts in "plumbing mode", and outputs

0 commit comments

Comments
 (0)