On 03/07/2019 08:36, David Kastrup wrote: > Chris Liddell <[email protected]> writes: > >> So, in essence, the idea is that you'll remove the stuff using >> GS_PDF_ProcSet entirely. Add the option -dDELAYBIND to your gs command >> line, include a suitable redefinition of initgraphics, then call >> .bindnow, and continue as before. >> >> The redefinition of initgraphics would look something like: >> >> /initgraphics { >> //initgraphics >> /RG where { >> pop <R value> <B value> <G value> 3 copy rg RG >> } if >> } bind def > > I'll probably pitch in from here (if nobody else does) and write code > that checks for the availability of any of these features and uses them. > > What will be the result of trying to use the broken DELAYBIND? Can I > check/use it in a manner where the worst that will happen is, well, > nothing?
Sorry, unfortunately not. Since DELAYBIND is a command line parameter, by the time any Postscript could detect the problem, it's already too late to recover. Using DELAYBIND without the fixes will result in almost any non-trivial file erroring out. Chris _______________________________________________ auctex-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/auctex-devel
