On Thu, Oct 22, 2015 at 11:27:56PM -0400, Paul A. Rubin wrote: > > On 10/22/2015 06:33 PM, Scott Kostyshak wrote: > >Actually I forgot to attach the .tex file. It is now attached (I BCC you > >just in case). Scott > Okay, we're getting a little clarity here. Your .tex file compiled and > displayed correctly. I dug a little deeper and discovered that, in addition > to the copy of dvipost.sty installed by the Synaptic package (which I had > uninstalled), there was a second copy lurking in my ~/texmf directory. I > suspect it was left over from a previous system upgrade. (System upgrades > don't touch my home partition.) For some reason, kpsewhich wasn't seeing it > but the LyX configuration script was.
Good work figuring that out. > So I manually deleted that folder, reconfigured LyX, and now dvi, ps2pdf and > dvipdfm all display changes correctly. Apparently the presence of dvipost > breaks change tracking output via those compilation methods. I wonder if the > change tracking code in LyX should be tweaked so that it never uses dvipost? Or it could be that LyX is not using dvipost correctly. That said, as you ask... > Is there a reason for it to be trying to use dvipost? It is not clear to me what the advantage is of using dvipost. Does anyone else know? Why require this dependency if things work well without it? Scott
