On 07/10/2016 05:26 AM, Andrew Parsloe wrote: > > > On 10/07/2016 5:42 p.m., Richard Heck wrote: >> On 07/10/2016 01:33 AM, Scott Kostyshak wrote: >>> On Sun, Jul 10, 2016 at 07:16:13AM +0200, Richard Heck wrote: >>>> commit d8aab4af9e6e72c835f78ba54a46687b870c25fa >>>> Author: Richard Heck <rgh...@lyx.org> >>>> Date: Sun Jul 10 01:12:42 2016 -0400 >>>> >>>> Fix thinko in Buffer::preview. It is possible for this routine to >>>> be called when we do not have a cloned Buffer, namely, if we >>>> do not >>>> have EXPORT_in_THREAD defined. >>> Thanks for fixing this. How does one set EXPORT_in_THREAD? I imagine >>> this could be useful for debugging purposes (e.g ruling out that a bug >>> is due to exporting in a separate thread). >> >> It's #defined in GuiView.cpp and GuiAlert.cpp. It's set in the code, but >> can be manually unset by people who don't want the risks of background >> export, threading, etc. And yes, it is useful for the purpose you >> mentioned. >> >> Probably, it should be exposed via configure, etc, but no one ever >> did that. >> >> Richard >> > > I ask in near total ignorance, but "my ears pricked up" when I read > "EXPORT_in_THREAD" and "It's set in the code, but can be manually > unset by people who don't want the risks of background export, > threading, etc." Is this a way to tackle > http://www.lyx.org/trac/ticket/8346 on the problems threaded export > poses for command-sequences?
Not really, unless you just want to disable background export entirely. The switch has to be set compile time. Richard
