A period after a parenthesis sometimes throws off linkify about bleach

[ndarville]

Same here; In[19] breaks. Maybe Gruber’s regex can be of help.

[jsocol]

Whoops, had the wrong output for 19 somehow.

I started with Gruber's regex, and I couldn't get it to compile, let alone match anything. If someone wants to take another crack at it, and it still passes the current test suite + fixes this, that would be awesome.

[ndarville]

If anything fails, I am sure that one of the guys at Stack Overflow will know what is wrong.

I tried Gruber’s regex in RegExr, and it works for the wonky example in our case—it doesn’t work with “cute” domains like del.icio.us, though. I’ll take a crack at it tomorrow, but with my meagre skills, I wouldn’t cross my fingers.

[jsocol]

Note how the TLDs are formatted into the regex right now. That's all the known-valid TLDs as of maybe 8 months ago, so things like del.icio.us get linkified but not example.txt.

[jsocol]

I don't think this is mathematically possible. We want http://en.wikipedia.org/wiki/X_(disambiguation) to match (e.g. the paren counts) and not http://this-is-the-end-of-a-parenthetical-comment.com/).. Frankly I'm impressed it works as well as it does. There are hacks in place for balanced parens around the link only, and those work great, but regex just can't do tag balancing. I think this errs on the right side.

[jsocol]

...of course, the github parser managed to linkify my examples there correctly. Maybe there's a non-regex way?

[jsocol]

As a test: example.com/).

Ah, no, this works for github/markdown because they only linkify links that start with https?: