jean-marc wrote,
> Richard> issue, and exactly what was happening. Then it was obvious
> Richard> :)
> Richard> I set those variables that are needed for other fonts in
> Richard> .cshrc, which I believe is the "normal" way to do it.
> Shoun't you put all these things in a .login?
.cshrc is the ".login" on debian when using tcsh. There's another one
(.bashrc ?) for bash. But this isn't executed before .xsession, and
thus they don't get passed.
> Richard> Would allowing entry of these paths (more particularly,
> Richard> directories to be added to any existing path) be a major
> Richard> issue? I really have no idea of what would be involved. But
> Richard> I think it's going to be an issue.
> You can always have a wrapper around LyX to do this. But fixing this
> just for LyX is not really a good idea, since people will have the
> same problem with other programs. And then, when you change something
> to TeX, you will have to modify configuration in several places.
The best way is probably to have my .xsession execute my .cshrc. I've
solved the problem at this end; I'm more worried about the number of
people who will hit it. I think we want to do *something*
preemptively, not necessarily chang lyxrc. Getting it into the docs or
a faq (Q: my fonts aren't always used, but sometimes they are. What's
going on. A: You're probably starting lyx from .xsession or some
other place that doesn't read your login configuration. fix it by ***)
will reduce bug reports later.
rick
--