Re: pdflatex not found?

[John Kitchin <jkitchin@andrew.cmu.edu>]

[-- Attachment #1: Type: text/plain, Size: 2700 bytes --]

This reminds me that I think I have this problem unless I open Emacs from a
command line.

On Tuesday, October 27, 2015, Nick Dokos <ndokos@gmail.com> wrote:

> Fatma Başak Aydemir <aydemirfb@gmail.com <javascript:;>> 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 <r.m.krug@gmail.com <javascript:;>> writes:
> >>
> >>> Envoyé de mon iPhone
> >>>
> >>>> Le 27 oct. 2015 à 01:14, Nick Dokos <ndokos@gmail.com <javascript:;>>
> a écrit :
> >>>>
> >>>> Peter Davis <pfd@pfdstudio.com <javascript:;>> writes:
> >>>>
> >>>>> Nick Dokos <ndokos@gmail.com <javascript:;>> 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
>
>
>
>

-- 
John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

[-- Attachment #2: Type: text/html, Size: 3997 bytes --]