On May 17, 2008, at 10:53 AM, Jean Magnan de Bornier wrote:

Le 17 mai à 10:11:13 Dalyoung Jeong écrit notamment:

| However, the same command worked well in a terminal.

...

| Maybe the system setup of yours is different from mine. | Usually I run "source .luatex" first before running luatex. | So my guess is that emacs couldn't know the luatex path even though it | is known in another program "terminal".

...

| Am I correct? If so, how to apply environment .luatex to global | condition? Otherwise, what are wrong in my setup?

Yes I think you are correct; if you start emacs *from this terminal from which you issued "source .luatex"* you will probably see that emacs knows luatex; this is what I had on my system, before I found how to have all my emacs know the proper environment. I am on linux and I believe you are on mac, so I'm not sure my experience can be extended to you?

If needed I will be more specific.

hth

Yes, you're both right. What I do (and what I find the easiest way): start emacs from the same terminal where you have issued "source .luatex" with the command "open -a emacs". That way, emacs should know about path variables. Thomas

On May 17, 2008, at 11:28 AM, Taco Hoekwater wrote:

Emacs has a setenv command, so you could "do" the whole setuptex in elisp with commands like this in your emacs startup script:

(setenv "TEXMF" "{$TEXMFOS,$TEXMFPROJECT,$TEXMFFONTS,$TEXMFLOCAL,$TEXMFEXTRA,!! $TEXMFMAIN}")

Maybe that is an idea?

Cheers, Taco

Yes, that would be possible (but you would also have to set the PATH variable). Another idea on Mac OS X is the use of an environment.plist which will set variables for all GUI applications. I'm not very much in favor of that, though, because it has created problems in the past with Geben Wierda's TeX installer. Since I spend much of my time in a terminal window anyway, I find it easiest to start emacs and/or gvim from there. Best Thomas