mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-09-11 13:01:28 +02:00
users/12100: default to a case-insensitive matcher with NO_CASE_GLOB
This commit is contained in:
parent
9fc8fe1785
commit
abdf734483
3 changed files with 21 additions and 1 deletions
|
@ -1,3 +1,9 @@
|
||||||
|
2007-10-25 Peter Stephenson <pws@csr.com>
|
||||||
|
|
||||||
|
* users/12100: Completion/Unix/Type/_path_files,
|
||||||
|
Doc/Zsh/compsys.yo: with NO_CASE_GLOB, use a case-insensitive
|
||||||
|
matcher if none is in effect.
|
||||||
|
|
||||||
2007-10-24 Peter Stephenson <p.w.stephenson@ntlworld.com>
|
2007-10-24 Peter Stephenson <p.w.stephenson@ntlworld.com>
|
||||||
|
|
||||||
* 24018: Doc/Zsh/mod_curses.yo, Src/Modules/curses.c:
|
* 24018: Doc/Zsh/mod_curses.yo, Src/Modules/curses.c:
|
||||||
|
|
|
@ -101,7 +101,16 @@ if (( $#ignore )); then
|
||||||
(( $mopts[(I)-F] )) || mopts=( "$mopts[@]" -F _comp_ignore )
|
(( $mopts[(I)-F] )) || mopts=( "$mopts[@]" -F _comp_ignore )
|
||||||
fi
|
fi
|
||||||
|
|
||||||
(( $#matcher )) && mopts=( "$mopts[@]" "$matcher[@]" )
|
if [[ $#matcher -eq 0 && -o nocaseglob ]]; then
|
||||||
|
# If globbing is case insensitive and there's no matcher,
|
||||||
|
# do case-insensitive matching.
|
||||||
|
matcher=( -M 'm:{a-zA-Z}={A-Za-z}' )
|
||||||
|
fi
|
||||||
|
|
||||||
|
if (( $#matcher )); then
|
||||||
|
# Add the current matcher to the options to compadd.
|
||||||
|
mopts=( "$mopts[@]" "$matcher[@]" )
|
||||||
|
fi
|
||||||
|
|
||||||
if zstyle -s ":completion:${curcontext}:" file-sort tmp1; then
|
if zstyle -s ":completion:${curcontext}:" file-sort tmp1; then
|
||||||
case "$tmp1" in
|
case "$tmp1" in
|
||||||
|
|
|
@ -1968,6 +1968,11 @@ quickly reduce the shell's performance. As a rough rule of thumb,
|
||||||
one to three strings will give acceptable performance. On the other
|
one to three strings will give acceptable performance. On the other
|
||||||
hand, putting multiple space-separated values into the same string does
|
hand, putting multiple space-separated values into the same string does
|
||||||
not have an appreciable impact on performance.
|
not have an appreciable impact on performance.
|
||||||
|
|
||||||
|
If there is no current matcher or it is empty, and the option
|
||||||
|
tt(NO_CASE_GLOB) is in effect, the matching for files is performed
|
||||||
|
case-insensitively in any case. However, any matcher must
|
||||||
|
explicitly specify case-insensitive matching if that is required.
|
||||||
)
|
)
|
||||||
kindex(max-errors, completion style)
|
kindex(max-errors, completion style)
|
||||||
item(tt(max-errors))(
|
item(tt(max-errors))(
|
||||||
|
|
Loading…
Reference in a new issue