Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15388 > unrolled thread
| Started by | Ilkka Virta <itvirta@iki.fi> |
|---|---|
| First post | 2019-09-21 12:34 +0300 |
| Last post | 2019-09-21 12:34 +0300 |
| 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: Incorrect example for `[[` command. Ilkka Virta <itvirta@iki.fi> - 2019-09-21 12:34 +0300
| From | Ilkka Virta <itvirta@iki.fi> |
|---|---|
| Date | 2019-09-21 12:34 +0300 |
| Subject | Re: Incorrect example for `[[` command. |
| Message-ID | <mailman.713.1569058490.2190.bug-bash@gnu.org> |
On 21.9. 03:12, hk wrote: > Thanks for the reply. I was wrong in my report. It does match values like > aab and aaaaaab in its original form. In some systems, yes. (It does that on my Debian, but doesn't work at all on my Mac.) > It is syntatically correct as a regular expression. [[:space:]]*?(a)b isn't a well-defined POSIX ERE: 9.4.6 EREs Matching Multiple Characters The behavior of multiple adjacent duplication symbols ( '+', '*', '?', and intervals) produces undefined results. https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/basedefs/V1_chap09.html -- Ilkka Virta / itvirta@iki.fi
Back to top | Article view | gnu.bash.bug
csiph-web