Jean-Marc Lasgouttes wrote: >>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: > > Angus> Well, I don't think that lyx should fork one script, wait for > Angus> it to finish generating a dvi file and then fork off another > to Angus> generate the bitmaps from it. However we could perhaps > generate Angus> a temporary file and use this to control the > conversion? > > This would indeed be bad if we want to use dvipng, which is able to > read from an unfinished dvi file, if I am not mistaken. > > Angus> It still feels like a fudge to me however... > > Another solution: have lyxpreview2bitmap.sh honor the setting of the > LATEX variable if it is already set in the environment. Then LyX > could set this variable when running lyxpreview2bitmap.sh. > > Still a kludge, but easy and transparent.
Ta-da! Simple solution to a simple problem. In fact, analogous to the LYX_USERDIR_14x environment variable, could we not get LyX itself to set a LYX_14X environment variable? Thereafter, we could simply ask lyx to supply us with the paths. Eg $ lyx --paths LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx-1.3.3cvs etc In fact, knowing thses paths, we could create a small library of useful shell functions... -- Angus
