From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: Nick Dokos <ndokos@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: pdflatex not found?
Date: Wed, 28 Oct 2015 13:40:31 +0100 [thread overview]
Message-ID: <m2a8r31800.fsf@polytechnique.org> (raw)
In-Reply-To: <f3d8527e9442420eacb98ec0551f60ed@exchsrv2.sgc.loc> (Malcolm Cook's message of "Tue, 27 Oct 2015 16:06:27 +0000")
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
On 2015-10-27 17:06, "Cook, Malcolm" <MEC@stowers.org> writes:
>>
> > John Kitchin <jkitchin@andrew.cmu.edu> 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.
>
> And, just to chime in late in the conversation, if your emacs was installed as
> an mac application using, say, http://emacsformacosx.com/ then you can start
> it from the command line as:
>
> open -a /Applications/path/to/emacs
>
> and get the environment variables you expect...
An alternative, that seems to be cross platform, is to populate
variables when emacs start. This is what I do here:
#+begin_src emacs-lisp
;; **** fetch env variables from zshrc
(let ((vars (split-string-and-unquote (shell-command-to-string ". ~/.zshrc; export") "\n")))
(mapcar (lambda (X) (let ((var_val (split-string-and-unquote X "=")))
(setenv (car var_val) (cadr var_val)))) vars)
(setq exec-path
(append
(split-string-and-unquote (getenv "PATH") ":")
exec-path)))
#+end_src
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated October 26, 2015, Mauna Loa Obs.): 398.51 ppm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-10-28 12:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 13:43 pdflatex not found? Peter Davis
2015-10-27 13:55 ` Fatma Başak Aydemir
2015-10-27 15:37 ` Nick Dokos
2015-10-27 15:48 ` Rainer M Krug
2015-10-27 15:51 ` John Kitchin
2015-10-27 15:58 ` Rainer M Krug
2015-10-27 16:06 ` Cook, Malcolm
2015-10-28 12:40 ` Alan Schmitt [this message]
2015-10-27 15:44 ` Rainer M Krug
2015-10-27 16:19 ` Nick Dokos
2015-10-27 16:45 ` Rainer M Krug
2015-10-27 17:02 ` Peter Davis
2015-10-27 17:50 ` Nick Dokos
2015-10-27 17:59 ` Peter Davis
2015-10-27 18:30 ` Rainer M Krug
2015-10-27 17:14 ` Nick Dokos
2015-10-27 15:40 ` Rainer M Krug
-- strict thread matches above, loose matches on Subject: below --
2015-10-27 16:12 Peter Davis
2015-10-27 16:40 ` Rainer M Krug
2015-10-26 22:18 Peter Davis
2015-10-27 0:14 ` Nick Dokos
2015-10-27 5:45 ` Rainer M Krug
2015-10-27 16:07 ` Charles C. Berry
2015-10-26 19:26 Peter Davis
2015-10-26 19:50 ` John Hendy
2015-10-26 20:29 ` Myles English
2015-10-26 21:43 ` Charles C. Berry
2015-10-26 20:03 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2a8r31800.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=MEC@stowers.org \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=ndokos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).