On Wed, Sep 17, 2014 at 4:14 PM, Richard Heck <rgh...@lyx.org> wrote: > On 09/17/2014 03:02 PM, Scott Kostyshak wrote: >> >> Are there any ideas for the message? Without thinking much, I will throw >> out: "xyz finished with an error. This was not previously reported in LyX so >> compilation is allowed to continue, but starting with LyX 2.2.0 this warning >> message will become an error and compilation will stop so that the user >> knows to fix the issue causing the error." > > > Minor tweaking: > > The external program > XYZ [[ probably on its own line, since these commands can be long ]] > finished with an error. Compilation will be [[ has been ?? I guess this > depends when the warning is issued. ]] allowed to continue, but starting > with LyX 2.2.0 this warning message will become an error and compilation > will stop. > > I don't think we need to explain in the dialog why that is. Though we could > add something like: We suggest you find the cause of the error.
Sounds good. > A few questions: Can this only happen during compilation? Or could it happen > during other sorts of export? Should that word be changed? Could it, in > particular, happen during compilation of instant preview? I don't use that, > but I can imagine it getting extremely annoying in this case to get that > message, especially if it were caused by something in the preamble that was > included in every single case. So, if that is an issue, perhaps we should > disable the error for preview. Good point. I will test this. Scott
