Andre Poenitz wrote: >> Actually, I suspect that this is not the cause of the problem. The >> real cause is that the directory trees have a different structure. >> On the Tru64 machine the equivalent of /home/aleem is >> /usr/users/aleem, so the necessary xfonts dir is not found: >> $ Adding /home/aleem/.lyx-1.3.3cvs/xfonts/ to the font path. >> xset: bad font path element (#59), possible causes are: >> Directory does not exist or has wrong permissions >> Directory missing fonts.dir >> Incorrect font server address or syntax > > Ah. And what happens if you manually run xset fp+ on the Tru64 box > before you start LyX?
Sorry, you've lost me. What are you trying to achieve? The mathed fonts are already found on the Tru64 machine when running LyX locally. 'xset -q' includes /usr/users/aleem/.lyx-1.3.3cvs/xfonts/ $ ls /usr/users/aleem/.lyx-1.3.3cvs/xfonts cmex10.pfb@ cmr10.pfb@ eufm10.pfb@ fonts.scale msbm10.pfb@ cmmi10.pfb@ cmsy10.pfb@ fonts.dir msam10.pfb@ wasy10.pfb@ If I now log on to the remote machine and fire up LyX on it, this remote copy of LyX tries to add /home/aleem/.lyx-1.3.3cvs/xfonts to the font path (which obviously fails), but this same font path should already be able to find the necessary fonts in /usr/users/aleem/.lyx-1.3.3cvs/xfonts. Or is my understanding of what should be happening fundamentally wrong? Anyway, somethings not working, 'cos I get the red rubbish ;-) If someone can explain what really happens, then that'd be great, otherwise don't bash your heads trying to get by box to work. I'm quite happy really with red rubbish ;-) -- Angus
