On Behalf Of Jamie Forth
> Sent: Thursday, 2 May 2019 20:53
> To: emacs-orgmode@gnu.org
> Subject: Re: [O] Problem with including file
>
> Hi Andreas,
>
> "Andreas Kiermeier" writes:
>
> > The reason I did tried to do it this way was because it's
Hi Andreas,
"Andreas Kiermeier" writes:
> The reason I did tried to do it this way was because it's simpler than
> having to say :export results for every source block.
> But, it a second call to
>
> #+PROPERTY: header-args+ :exports code
> Just before the #+INCLUDE gets everything working perf
Thanks for the quick reply.
Of course you are spot on, Nicolas.
Changing to
#+PROPERTY: header-args+ :exports code
Or
#+PROPERTY: header-args+ :exports both
Does indeed fix the problem.
The reason I did tried to do it this way was because it's simpler than
having to say :export results for every
Hi Sharon,
The tex file is straight out of the export, and the second ”}” matches the
“\hypersetup{“ a few lines earlier.
Thanks,
Andreas
From: Sharon Kimble
Sent: Thursday, 2 May 2019 17:57
To: Andreas Kiermeier
Cc: emacs-orgmode@gnu.org
Subject: Re: [O] Problem with including file
Hello,
"Andreas Kiermeier" writes:
> --- begin test.org
>
> #+STARTUP: content indent hidestars fninline
>
> #+PROPERTY: header-args:R :session *R* :cache no
>
> #+PROPERTY: header-args+ :results output
>
> #+PROPERTY: header-args+ :exports results
Here, you prevent source blocks' contents
"Andreas Kiermeier" writes:
Andreas.
Just a very quick glance at your problem, and in the tex output you've shown
there is a double closing bracket on 'pdflang={English}}'. If you correct that
then your output might be better, I don't know, but its certainly worth a try.
Thanks
Sharon.
> Hi,
Hi,
I've just run into a problem with exporting a file to latex.
In a nutshell, my org files usually contain various analyses and output in
R.
I generally don't include the source in the file, but instead tangle all
source blocks at the end and include the source code file in an Appendix.
This h
