On 9/28/12 12:52 AM, hans1wo...@gmail.com wrote:
>> The question is whether or not !(x) should match the empty string. The
>> bash matcher treats it similarly to [!x], which does not.
>
> It does however match the empty string at most times. So I guess that's the
> real bug. Again, there is some inconsistency in
It's whether or not it matches the NUL at the end of the search string. I
agree that it should, or at least that (x) should not match, so !(x)
should, and that will be fixed for the next version.
> [OT] Thanks for your work for the Bash project. I've just learned that you've
> been the main maintainer for a long time, so keep it up! :)
:-)
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
