Skip to main content
Post Closed as "Duplicate" by CommunityBot
edited tags
Link
Govind Rai
  • 185
  • 1
  • 3
  • 13
added 81 characters in body
Source Link
Govind Rai
  • 185
  • 1
  • 3
  • 13

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 andan 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 very harder to debug.

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 and error immediately, but for CD .. nothing is displayed.

Also, if the error is being suppressed by default, is there a way to have it throw an error?

My biggest concern is no errors are thrown, and I am under the impression my commands are actually working making it very harder to debug.

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.

Source Link
Govind Rai
  • 185
  • 1
  • 3
  • 13

Why doesn't CD .. throw an error but other incorrect commands do? How to have it give me an error?

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 and error immediately, but for CD .. nothing is displayed.

Also, if the error is being suppressed by default, is there a way to have it throw an error?

My biggest concern is no errors are thrown, and I am under the impression my commands are actually working making it very harder to debug.