On Tue, Jan 21, 2003 at 02:12:42PM +0000, Angus Leeming wrote:
> Is this your way of saying that the problem lies in mathed itself?
> Ie, it would go away if we had control over the 'true' passed to the
> WriteStream c-tor.
We could certainly use that, but I don't know what the 'nice' flag is good
for, either. I thought it is _just_ for linebreaking, so the question
whether \lyxlock should get written should not depend on that flag.
> Here's a minimal "solution" from the preview end rather than the
> mathed end. We currently generate a latex file for preview-latex by:
>
> 1 Dump LyX preamble.
> 2 Dump the math-macros
> 3 Add preview-latex magic
> \begin{document}
> 4 Dump all previewable snippets.
> \end{document}
>
> A hack might be to redefine \lyxlock between 1 and 2 as an empty
> wrapper. Care to suggest a bit of LaTeX that would do this?
\def\lyxlock{}
That can even go to the top of the file.
> Alternatively, we could post-process the data passed to os by the
> math insets before it is dumped to file to remove these lyxlocks.
> That, however, sounds nastier.
Nah...
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
