Richard Heck <rgheck <at> comcast.net> writes:
> > > Untested patch attached. But I think something like this is what needs > doing. Anyone who wishes should feel free to play with it and commit it > if it seems to work. As the bug appears in 2.0.1 due to changeset 38746, you might revert this one and solve the problem in trunk (where the problem exists as well). You might backport the TEXINPUTS stuff, once solved in trunk, later for 2.0.2, I guess we can't remain in string freeze too long. -- Jean-Pierre
