@@ -157,20 +157,20 @@ As shown below, you may simply clone the GitHub repo and source the files requir
157
157
(You should probably fork it instead to keep your customisations)
158
158
159
159
``` Shell
160
- $ git clone https://github.com/bash-my-aws/bash-my-aws.git ~ /.bash-my-aws
160
+ $ git clone https://github.com/bash-my-aws/bash-my-aws.git ${BMA_HOME :- $HOME / .bash-my-aws}
161
161
```
162
162
163
163
Put the following in your shell's startup file:
164
164
165
165
``` Shell
166
- export PATH=" $PATH :$HOME /.bash-my-aws/bin"
167
- source ~ /.bash-my-aws/aliases
166
+ export PATH=" $PATH :${BMA_HOME :- $ HOME/ .bash-my-aws} /bin"
167
+ source ${BMA_HOME :- $HOME / .bash-my-aws} /aliases
168
168
169
169
# For ZSH users, uncomment the following two lines:
170
170
# autoload -U +X compinit && compinit
171
171
# autoload -U +X bashcompinit && bashcompinit
172
172
173
- source ~ /.bash-my-aws/bash_completion.sh
173
+ source ${BMA_HOME :- $HOME / .bash-my-aws} /bash_completion.sh
174
174
```
175
175
176
176
!!! note "Why use shell aliases?"
@@ -184,11 +184,13 @@ source ~/.bash-my-aws/bash_completion.sh
184
184
the functionaility, simplicity and discoverability of the project. Massive thanks
185
185
to [@ninth-dev](https://github.com/ninth-dev) for this.
186
186
187
-
187
+ ``` Shell
188
188
# bash users may source the functions instead of loading the aliases
189
- if [ -d ${HOME}/.bash-my-aws ]; then
189
+ if [ -d ${BMA_HOME:- $HOME / .bash-my-aws} ]; then
190
+ for f in ${BMA_HOME:- $HOME / .bash-my-aws} /lib/* -functions; do source $f ; done
190
191
for f in ~ /.bash-my-aws/lib/* -functions; do source $f ; done
191
192
fi
193
+ ```
192
194
193
195
## Usage
194
196
0 commit comments