@@ -31,22 +31,22 @@ make install # as root
31
31
```
32
32
33
33
These commands installs the completions and helpers, as well as a
34
- profile.d script that loads bash_completion where appropriate. If
34
+ profile.d script that loads ` bash_completion ` where appropriate. If
35
35
your system does not use the profile.d directory (usually below
36
36
` /etc ` ) mechanism, i.e. does not automatically source shell scripts in
37
37
it, you can source the ` $sysconfdir/profile.d/bash_completion.sh `
38
38
script in ` /etc/bashrc ` or ` ~/.bashrc ` .
39
39
40
40
The profile.d script provides a configuration file hook that can be
41
- used to prevent loading bash_completion on per user basis when it's
41
+ used to prevent loading ` bash_completion ` on per user basis when it's
42
42
installed system wide. To do this, turn off programmable completion
43
43
with ` shopt -u progcomp ` in ` $XDG_CONFIG_HOME/bash_completion `
44
44
(` ~/.config/bash_completion ` if ` $XDG_CONFIG_HOME ` is not set), and
45
45
turn it back on for example in ` ~/.bashrc ` if you want to use
46
46
programmable completion for other purposes.
47
47
48
48
If you're using MacOS X, ` /etc/bashrc ` is apparently not sourced at
49
- all. In that case, you can put the bash_completion file in ` /sw/etc `
49
+ all. In that case, you can put the ` bash_completion ` file in ` /sw/etc `
50
50
and add the following code to ` ~/.bash_profile ` :
51
51
52
52
``` shell
@@ -130,7 +130,7 @@ A. Install it in one of the directories pointed to by
130
130
for more than one command. The other one which is present for
131
131
backwards compatibility reasons is ` compatdir ` (get it with
132
132
` pkg-config --variable=compatdir bash-completion ` ) from which files
133
- are loaded when bash_completion is loaded.
133
+ are loaded when ` bash_completion ` is loaded.
134
134
135
135
For packages using GNU autotools the installation can be handled
136
136
for example like this in ` configure.ac ` :
0 commit comments