From my understanding, bash is case sensitive. So cd ..
would work and CD ..
wouldn't.
However, inputting CD ..
doesn't throw any errors (it doesn't do anything). Why is that? If I type an incorrect command such as ls-a
instead of ls -a
the terminal throws an error immediately, but for CD ..
nothing is displayed. In fact, I thought it actually worked until I took a closer look at my directory.
Also, if the error is being suppressed by default, is there a way to have it throw an error?
My biggest concern is that no errors are being thrown, and I am under the false impression my commands are actually working making it harder to debug.
CD
command is:type CD
. – Nominal Animal Nov 07 '16 at 21:49CD is hashed (/usr/bin/CD)
– Govind Rai Nov 07 '16 at 21:50cD
work, too? – Mark Plotnick Nov 07 '16 at 21:50CD
orcD
work. Neither thrown an error either. They do nothing. – Govind Rai Nov 07 '16 at 21:52osx
tag. I think there's already a question and answer that's a dup of this. – Mark Plotnick Nov 07 '16 at 21:53LS
andls
work, however. So there seems to be both case sensitivity and case insensitivity... – Govind Rai Nov 07 '16 at 21:56