Georg Brandl

Thanks! Could you please update the documentation of the parameter (in the docstring of `ImageFormatter`)?

Hmm, since the lexer is not instantiated properly in the other process (I assume it is shipped in pickled form) the processed tokendefs are missing. We should probably either raise...

This can probably also be simplified a lot. We don't need to verify the 0-255 range for octets, for example.

Yes, this one is a bit problematic... Since the C family declaration syntax is so complex and not using keywords, there's basically no chance to categorize these correctly with the...

In general I'm fine with changing the name, but we need a compatibility alias for the lexer class in the `perl` module. The `agile` module is for compatibility only, so...

There isn't. I also think that regular expressions don't really fit the "language" concept too well that they could benefit from highlighting.

Strange, I don't understand how the lexer leaves the `blockname` state without producing an error...

For both cases, the `blockname` state has no "exit" condition. I now re-read the code, and the lexer has an implicit "return to root state" if at line end and...

@fcurella want to make another try at a PR, here on github?

I'm -1 on this change. Not only is it backwards incompatible and slows down loading of lexers for most users, it also allows any installed package to override core lexers,...