zsh:options: Make globbing sensitive to case

I am not sure why I had this activated.

Case insensitive globbing can still be achieved by using the Globbing
Flag `i`.
This commit is contained in:
2022-12-28 17:05:15 +01:00
parent 616988560a
commit 8da38e9224

View File

@@ -67,19 +67,18 @@
# there are no more matches, go back to the first one again.
# reverse-menu-complete may be used to loop through the list in the other
# direction. This option overrides AUTO_MENU.
setopt NO_MENU_COMPLETE
# Expansion and Globbing #######################################################
# Do not unset CHASE_GLOB under android as then globbing with absolute paths
setopt NO_MENU_COMPLETE
# Expansion and Globbing #######################################################
# Make globbing (filename generation) sensitive to case. Note that other
# uses of patterns are always sensitive to case. If the option is unset,
# the presence of any character which is special to filename generation will
# cause case-insensitive matching. For example, cvs(/) can match the
# the presence of any character which is special to filename generation will
# cause case-insensitive matching. For example, cvs(/) can match the
# directory CVS owing to the presence of the globbing flag (unless the
# option BARE_GLOB_QUAL is unset).
#
# NOTE: Do not unset CHASE_GLOB under android as then globbing with absolute
# paths breaks as the PWD is often in a path with subdirectories that are
# owned by root and not world-readable (e.g. /data/data/). I *believe* this
# is the reason for it.