Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15497 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-10-11 10:09 -0400 |
| Last post | 2019-10-11 10:09 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: nocaseglob and RE matching Chet Ramey <chet.ramey@case.edu> - 2019-10-11 10:09 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-10-11 10:09 -0400 |
| Subject | Re: nocaseglob and RE matching |
| Message-ID | <mailman.328.1570802977.9715.bug-bash@gnu.org> |
On 9/23/19 1:38 PM, Grisha Levit wrote: > Currently nocaseglob and nocasematch both control case insensitivity > of RE matching (in lib/sh/smatch.c): > > if (glob_ignore_case || match_ignore_case) > rflags |= REG_ICASE; > > However, the documentation suggests that only nocasematch should have > this effect. I'm guessing this behavior was in bash-3.1 for > compatibility with bash-3.0 (in which nocaseglob *was* the documented > way to turn on case insensitive RE matching, prior to nocasematch > being added) but it doesn't seem to make much sense now. Yeah, it's probably time to remove the glob_ignore_case. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web