Recursive load of out of place custom config files
parent
517d4b2ca4
commit
3e60efd19d
|
|
@ -154,7 +154,7 @@ For custom scripts, and aliases, just create the following files (they'll be ign
|
|||
|
||||
Anything in the custom directory will be ignored, with the exception of `custom/example.bash`.
|
||||
|
||||
Alternately, if you would like to keep your custom scripts under version control, you can set `BASH_IT_CUSTOM` in your `~/.bashrc` to another location outside of the `~/.bash_it` folder.
|
||||
Alternately, if you would like to keep your custom scripts under version control, you can set `BASH_IT_CUSTOM` in your `~/.bashrc` to another location outside of the `~/.bash_it` folder. In this case, any `*.bash` file under every directory below `BASH_IT_CUSTOM` folder will be used.
|
||||
|
||||
## Themes
|
||||
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ do
|
|||
done
|
||||
|
||||
# Custom
|
||||
CUSTOM="${BASH_IT_CUSTOM:=${BASH_IT}/custom}/*.bash"
|
||||
CUSTOM="${BASH_IT_CUSTOM:=${BASH_IT}/custom}/*.bash ${BASH_IT_CUSTOM:=${BASH_IT}/custom}/**/*.bash"
|
||||
for config_file in $CUSTOM
|
||||
do
|
||||
if [ -e "${config_file}" ]; then
|
||||
|
|
|
|||
Loading…
Reference in New Issue