@@ -157,20 +157,20 @@ As shown below, you may simply clone the GitHub repo and source the files requir
157157(You should probably fork it instead to keep your customisations)
158158
159159``` 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}
161161```
162162
163163Put the following in your shell's startup file:
164164
165165``` 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
168168
169169# For ZSH users, uncomment the following two lines:
170170# autoload -U +X compinit && compinit
171171# autoload -U +X bashcompinit && bashcompinit
172172
173- source ~ /.bash-my-aws/bash_completion.sh
173+ source ${BMA_HOME :- $HOME / .bash-my-aws} /bash_completion.sh
174174```
175175
176176!!! note "Why use shell aliases?"
@@ -184,11 +184,13 @@ source ~/.bash-my-aws/bash_completion.sh
184184 the functionaility, simplicity and discoverability of the project. Massive thanks
185185 to [@ninth-dev](https://github.com/ninth-dev) for this.
186186
187-
187+ ``` Shell
188188 # 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
190191 for f in ~ /.bash-my-aws/lib/* -functions; do source $f ; done
191192 fi
193+ ```
192194
193195## Usage
194196
0 commit comments