emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: passing LC_ALL environment variable to org export call
Date: Mon, 29 Sep 2014 14:06:17 +0200	[thread overview]
Message-ID: <87y4t2ws06.fsf@gmx.us> (raw)
In-Reply-To: 93730A3A-00B0-431D-8498-7D7852D15AAA@gmail.com

Johannes Rainer <johannes.rainer@gmail.com> writes:

> thanks for your hint. I checked Sys.getenv before and after the
> failing code, but LC_ALL was always properly set. I’m afraid my
> problem relates to some Mac LLVM and GCC gfortran compiler thing,
> since I’m using a R version compiled against the Mac Accelerate
> framework (vecLib)… it is just so strange that I only get the error in
> Emacs org-mode upon exporting the org file, but not, if I evaluate
> each code chunk separately.

But are you using .C, .Fortran or Rcpp in your code-block?  If not,
why would your compilers matter?  (I'm not an expert on R internals,
so my comment may be naïve).

As a short turn solution try to add this to the top of your file

#+PROPERTY: session *R*

These days you might even get away with just 

#+PROPERTY: session

I'm not sure.  This should run your code from the same session.

[This should be equivalent to adding :session to babel blocks, but
 check the manual if it ain't working]

> to set all environment variables I’m using the “exec-path-from-shell”
> extension, so, all environment settings from the shell are available
> in Emacs.

Are you exporting async or "normally"?  If async, do you get the error
when exporting "normally"?

—Rasmus

-- 
Hvor meget poesi tror De kommer ud af et glas isvand?

  reply	other threads:[~2014-09-29 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26  9:14 passing LC_ALL environment variable to org export call Johannes Rainer
2014-09-26 13:56 ` Rasmus
2014-09-29 10:54   ` Johannes Rainer
2014-09-29 12:06     ` Rasmus [this message]
2014-09-29 12:51       ` Johannes Rainer

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=87y4t2ws06.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    /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).