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
Many common utilities, including git use case sensitivity.
Is this in the Posix standard? Need link here if so.
I'm not sure it outright says options are case sensitive; but it specifies the ls utility with distinct -A and -a options, and Utility Syntax Guidelines specifically reserve upper-case -W for vendor options.
There was a lot of discussion around this when we first started. There are a lot of conflicting things in the wild. We landed on case sensitive, as it is easier to loosen those requirements in the future vs trying to tighten them. As mentioned above, many of the examples we found where there were casing differences were often short (single letter) options. We did not find many longer named identifiers that had different behavior based only on casing.
Should command lines be treated as case sensitive?
Case sensitive CLIs have different behavior for
-x
and-X
, for example.Arguments for case sensitivity
Many common utilities, including
git
use case sensitivity.Is this in the Posix standard? Need link here if so.
There are more possibilities for identifiers if case is recognized
Arguments for **in-*sensitivity
The PowerShell and Windows command prompt are case -insensitive.
Questions
No. This would change the case of arguments, as well as CLI syntax
The text was updated successfully, but these errors were encountered: