Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15419 > unrolled thread
| Started by | Grisha Levit <grishalevit@gmail.com> |
|---|---|
| First post | 2019-09-23 13:38 -0400 |
| Last post | 2019-09-23 13:38 -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.
nocaseglob and RE matching Grisha Levit <grishalevit@gmail.com> - 2019-09-23 13:38 -0400
| From | Grisha Levit <grishalevit@gmail.com> |
|---|---|
| Date | 2019-09-23 13:38 -0400 |
| Subject | nocaseglob and RE matching |
| Message-ID | <mailman.919.1569260347.2190.bug-bash@gnu.org> |
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.
Back to top | Article view | gnu.bash.bug
csiph-web