On Fri, Oct 23, 2009 at 06:42 AM, Guenter Milde wrote: >On 2009-10-23, rgheck wrote: >> On 10/22/2009 08:01 PM, Ernesto Posse wrote: >>>> On 10/15/2009 08:36 PM, Ernesto Posse wrote: > >>>>> I have some very strange behaviour in LyX. I have a simple latex style >>>>> file (mystyle.sty) which is located in a directory "mylatexfiles". >>>>> latex knows about this: I have "export TEXINPUTS=mylatexfiles:" in my >>>>> bash login[...]. > >... > >>> I've given the full path, and I still have the same issue. > >It should work with the full *absolute* path. LyX runs the latex >conversion in a temporary directory, so a relative path will not work.
I used export TEXINPUTS=~/Setup/mytexmf/tex/latex: which is supposed to be expanded to an absolute path. >>> How come TeX from the command line finds it but TeX invoked by LyX >>> does not find it? > >Does it work if you start LyX from an x-terminal? The bash login file >is not read at X-startup. and if you just click on a LyX icon lyx does >not see your login environment variables. Right, I figured out that, so I changed the TEXMFHOME variable in /etc/texmf/texmf.d/05TeXMF.cnf file (I don't like the default ~/texmf), then I ran sudo update-texmf and I ran sudo texhash, as well as mktexlsr in my texmf tree which created the ls-R file. Running sudo texconfig confirmed the new value for TEXMFHOME. I reconfigured LyX, and rebooted. Now it works, but I don't like the fact that I had to update central (non-user-specific) files to do this. Is there any way I could have my own TEXMFHOME, different than ~/texmf without having to modify any system-wide files? >Günter Thanks -- Ernesto Posse Applied Formal Methods Group - Software Technology Lab School of Computing Queen's University - Kingston, Ontario, Canada
