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
27/10/15 14:43 tarihinde Peter Davis yazdı:
Rainer M Krug <r.m.k...@gmail.com> writes:
Envoyé de mon iPhone
Le 27 oct. 2015 à 01:14, Nick Dokos <ndo...@gmail.com> a écrit :
Peter Davis <p...@pfdstudio.com> writes:
Nick Dokos <ndo...@gmail.com> 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?
And you say it should be in /usr/texbin - what happens if you invoke
it with an absolute path: "/usr/texbin/pdflatex" in your shell?
Imiight have missed it - but which OS are you using?
Sorry. It's OS X 10.10.5, using GNU Emacs 24.5.1
Thanks!
-pd
--
--------------------------------
Fatma Başak Aydemir
PhD Student at ICT International Doctoral School
Department of Information Engineering and Computer Science
University of Trento
Skype: fatmabasak.aydemir
E-mail: ayde...@disi.unitn.it
