You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I then run the following, which makes it work properly.
$ source ~/.oh-my-bash/custom/aliases/example.aliases.sh
$ alias ll
alias ll='ls -lAhtrF --group-directories-first'
My .bashrc does source "$OSH"/oh-my-bash.sh, which again should load and overwrite custom settings over default oh-my-bash settings. However, when I start a new instance of Windows' Terminal (or simply a new tab within) running Git Bash it does not automatically source and overwrite my custom alias. Why does it not work?
The text was updated successfully, but these errors were encountered:
@akinomyoga: "Did you add example in the array aliases in your .bashrc? You need to add example in the arrray aliases in your .bashrc to enable example.aliases.sh."
this is indeed to way to do it. It is however very much not intuitive on how to practically do that.
I guess most people will not use the example.aliases.sh but put their own files in there.
If that is what you are doing you have to exactly use the exact naming schema of examples.aliases.sh for such files.
Just my_aliases.sh does not do the trick.
you need a full my_aliases.aliases.sh schema as filenames and then ...
reference to it with the part before ....aliases.sh of the mandatory ending ind the aliases array of your .bashrc in order for this to work.
Running
ll
uses the default.I then run the following, which makes it work properly.
My
.bashrc
doessource "$OSH"/oh-my-bash.sh
, which again should load and overwrite custom settings over default oh-my-bash settings. However, when I start a new instance of Windows'Terminal
(or simply a new tab within) running Git Bash it does not automatically source and overwrite my custom alias. Why does it not work?The text was updated successfully, but these errors were encountered: