Hi, * Fabian Groffen wrote:
I would just appreciate either of both patches to make it to the mutt sources though.
Since the change is in the legacy regex engine for systems with broken regex implementations, I personally don't have a problem with patching it.
But I wonder whether we should a) update it in case we continue to ship it for legacy systems and/or b) disable the configure switch to make sure it's really used as fallback only in case configure finds the current implementation non-existent or broken. (though I guess for option b) we can't write simple tests with a broad coverage of things which could be broken)
Regards, Rocco