John Kitchin writes: > This reminds me that I think I have this problem unless I open Emacs from a > command line. Yup - this is one way of circumvent the problem: by starting emacs from the command line. > > On Tuesday, October 27, 2015, Nick Dokos wrote: > >> Fatma Başak Aydemir > writes: >> >> > I do not know the reasons but I had the same problem in the past on OS X. >> > >> > exec-path-from-shell package is a nice solution for that. >> > >> > https://github.com/purcell/exec-path-from-shell >> > >> >> Just the need for a package like that indicates that something is badly >> broken on OS X, I think. To be fair, it's a mess on Linux as well, but >> it is possible to make sure that variables you define (and export) in >> your .profile get propagated to applications started by the DE/WM. In my >> current installation (Fedora 21), that is done by >> /etc/X11/xinit/xinitrc-common, which does this: >> >> [ -r $HOME/.profile ] && . $HOME/.profile >> >> Maybe OS X has a "hidden" mechanism like this? >> >> > 27/10/15 14:43 tarihinde Peter Davis yazdı: >> >> Rainer M Krug > writes: >> >> >> >>> Envoyé de mon iPhone >> >>> >> >>>> Le 27 oct. 2015 à 01:14, Nick Dokos > >> a écrit : >> >>>> >> >>>> Peter Davis > writes: >> >>>> >> >>>>> Nick Dokos > writes: >> >>>> ... >> >>>> Yes, probably, but if I can get people to submit backtraces when >> getting >> >>>> an error, we can cut down the email volume by a factor of 2.43 >> (making up >> >>>> fictitious data to bolster my case...) In all seriousness, at least it >> >>>> shows that you are not going down some strange path. >> >> I think the actual number is more like 2.17, but let's not quibble. >> >> >> >>>> What happens if you say M-x shell-command RET pdflatex RET? >> >> Not found. >> >> >> >>>> Somebody suggested running "which pdflatex" in your shell - what does >> >>>> that say? >> >> Still not found. However, adding it to ~/.tcshrc seems to fix the >> >> problem. That makes sense, but leaves two questions: >> >> >> >> 1) Why am I able to run pdflatex (without specifying the path) just >> >> from the shell running in a terminal window? >> >> >> >> 2) What's the point of defining the emacs exec-path, since I needed >> >> to define the shell's PATH variable anyway? >> >> >> >> FWIW, I never define exec-path explicitly: it is set from my $PATH when >> emacs starts. >> >> -- >> Nick >> >> >> >> -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D): +49 - (0)3 21 21 25 22 44 email: Rainer@krugs.de Skype: RMkrug PGP: 0x0F52F982