Open magnusfar opened 7 months ago
My
.bashrc
doessource "$OSH"/oh-my-bash.sh
, which again should load and overwrite
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
.
@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.
my_aliases.sh
does not do the trick. my_aliases.aliases.sh
schema as filenames and then .......aliases.sh
of the mandatory ending ind the aliases
array of your .bashrc in order for this to work.https://github.com/ohmybash/oh-my-bash/pull/499 should enhance the situation
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?