Jon Schlinkert

Hi, thanks for creating an issue. > Should this not match or is it a bug? Please add a comparison of how bash handles these extglob patterns versus this library

> That seems like such incorrect behavior... which result?

do the following instead: ```js console.log(extglob.makeRe('*.!(js|json)').test('a.js.gz')); // true console.log(extglob.makeRe('*.!(js|json)').test('a.json.gz')); // true console.log(extglob.makeRe('*.!(js|json)').test('a.gz')); // true ``` Even bash yields incorrect results sometimes when globs are nested inside negation globs. In javascript,...

btw, on a totally unrelated note, if you happen to notice [this table being corrupted](https://github.com/micromatch/extglob#extglob-cheatsheet), that's a bug in github's markdown parser.

I'm thinking this looks like a bug then. I try to stick to bash behavior, but sometimes bash is unable to handle certain patterns. In this case, it seems like...

Agreed, it's irritating that NPM picked up this file when I published the lib, despite always being ignored in [.gitignore](https://github.com/micromatch/extglob/blob/master/.gitignore#L2).

> Maybe got committed by mistake at some point? Remember that NPM doesn't care what is committed to git. It only zips up what you explicitly define in package.json.

> full disclosure: I'm learning here, never actually published to npm before No worries! I don't mind the questions. Happy to help! > but wouldn't you still need it in...

fwiw I will republish to get rid of this file as soon as I have a chance

> Then I need to manually delete this file and run again. Damn that's irritating. Sorry you have to do that. I've been swamped, I'll try to push up a...