Hi all,
I have a question about exporting source code blocks. Say, I have
several modules (mod1, mod2), that build a bigger part (part1) of my
program, e.g.:
#+srcname: mod1
#+begin_src R :tangle no :export code
print("mod1")
#+end_src
#+srcname: mod2
#+begin_src R :tangle no :ex
So, is this not possible right now?
Cheers,
Andreas
Am 07.12.2010 19:37, schrieb Thomas S. Dye:
> Aloha Andreas,
>
> Perhaps :noweb tangle will do what you want.
>
> hth,
> Tom
>
> On Dec 7, 2010, at 7:38 AM, Andreas Leha wrote:
>
>> Hi all,
>>
>>
Am 07.12.2010 20:33, schrieb Thomas S. Dye:
> Aloha Andreas,
>
> On Dec 7, 2010, at 8:49 AM, Andreas Leha wrote:
>
>> Hi Tom,
>>
>> thanks for this answer. This indeed comes closer to what I want.
>>
>> But, some comments:
>>
>> (1) There see
t; session gets a name.
>
> All the best,
> Tom
>
>
> On Dec 7, 2010, at 9:46 AM, Andreas Leha wrote:
>
>> Hi Tom,
>>
>> thanks for the answer and thanks for spotting the typo. But even
>> with the typo corrected during export the noweb links are sti
Hi all,
has the feature of captions for source code blocks made any progress
(see http://thread.gmane.org/gmane.emacs.orgmode/27896/focus=27913)?
I am very interested in this feature for the latex listings package.
Regards,
Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
___
Hi all,
(how) can I have source code block in lists not breaking the latex
exported list?
Example:
* Test
1) this is the first item
#+srcname: code
#+begin_src R :tangle no :export code
print("some code")
#+end_src
which has some code
2) this is the second item
Th
us message) and then cross
> reference it from the list.
>
> * Test
> 1) this is the first item (Listing \ref{fig:first-code})
> 2) this is the second item (Listing \ref{fig:second-code})
>
> But this might not be what you're after.
>
> All the best,
> Tom
>
ripts, which complain about the float
> package, something like this should work:
>
> \DeclareNewTOC[type=listing,name=Listing,float,floatpos=htb!]{lol}
> \newcommand\listoflistings{\listoftoc[List of Listings]{lol}}
>
> hth,
> Tom
>
> On Dec 8, 2010, at 1:10 PM,
Hello Nicolas,
I can confirm that this is fixed now. Thanks a lot!
Greetings,
Andreas
Am 09.12.2010 21:36, schrieb Nicolas Goaziou:
> Hello,
>
>
>>>>>> Andreas Leha writes:
>>>>>>
>
>> Hi all, (how) can I have source
Hi all,
is there an option (source block header argument) that allows to disable
the evaluation of the block, but still allows C-c C-c to perform the
evaluation?
The header argument ':eval never' disables the evaluation completely.
I'd like the C-c C-c to take precedence over this.
So I guess I a
t; Hi Andreas,
>
> Andreas Leha wrote:
>
>> is there an option (source block header argument) that allows to disable the
>> evaluation of the block, but still allows C-c C-c to perform the evaluation?
>> The header argument ':eval never' disables the evaluation comp
Hi all,
is it possible to set *per buffer* the option whether to center tables
in the LaTeX output?
I tried
#+BIND: org-export-latex-tables-centered nil
#+TITLE: Test Centered Tables
* Test
| col1 | col2 | col3 |
|--+--+--|
|1 |2 |3 |
But this does not work.
Hi all,
I found a severe bug that actually eats my text, i.e. *destroys* my
org-mode file.
Or am I missing something here?
Just try that:
--8<---cut here---start->8---
* Test
Execute this once:
#+BEGIN_src R :session test :results output silent :exports
FSF papers are signed and the process is completed - so the revert can
be reverted now (the patch should still apply).
Sorry for the long delay...
Hi all,
there is a significant performance drop connected to (the quite old) commit
8c37281cb63a0b5cb0d84d22960e3a33d7680d40
ob-tangle: continued code blocks now implemented with the :noweb-ref header arg
which introduces the continued code blocks.
On the test file ([fn:1] for the old syntax, [
Hi Eric,
thanks for looking into this providing a patch already!
> I've just pushed up a patch which should speed up the collection of
> continued source blocks. Please let me know if the performance increase
> is sufficient for your example, if not we can look at more dramatic
> methods of opt
Hi Eric,
Eric Schulte writes:
> Andreas Leha writes:
>
>> Hi Eric,
>>
>> thanks for looking into this providing a patch already!
>>
>>> I've just pushed up a patch which should speed up the collection of
>>> continued source blocks.
Hi,
@Tom, thanks for this nice snippet! Very useful, when several emacs
frames are opened.
While it works well on my emacs23, the emacs24 snapshot from
http://emacs.naquadah.org/ crashes, when I select a template. Is this a
general issue with emacs24? Ideas to adapt the snippet to work with
em
Hi all,
I have several code blocks that must be evaluated during export, but
silently, i.e. I do not want code/output/anything to appear in the export.
How do I achieve this? The obvious :export none also disables evaluation.
Regards,
Andreas
smime.p7s
Description: S/MIME Cryptographic Signa
Hi all,
just found out: the inline block works when I explicitly state :results
replace.
So both questions from the previous email collapse to: why is that
necessary?
Regards,
Andreas
Am 04.02.2011 17:13, schrieb Andreas Leha:
> Hi all,
>
> I have two questions:
>
> (1) How
Hi all,
I have two questions:
(1) How do I get resuts from code block evaluation (e.g. a single
number) inline into text during (LaTeX-)export? Something like: We use
a level of #+call: getLevel()
(2) Why do these two subheadings produce different output during
(LaTeX-)export?
* Test
** Norm
Hi Dan,
thanks. That's what I was looking for. Works perfectly.
Cheers,
Andreas
Am 04.02.2011 17:25, schrieb Dan Davison:
> Andreas Leha writes:
>
>
>> Hi all,
>>
>> I have several code blocks that must be evaluated during export, but
>> silently, i
Hi Dan,
Thanks for looking into this and for providing a patch that fast!
Andreas
Am 04.02.2011 18:11, schrieb Dan Davison:
> Andreas Leha writes:
>
>
>> Hi all,
>>
>> just found out: the inline block works when I explicitly state :results
>> replace.
n.
>
> http://www.mail-archive.com/[email protected]/msg29333.html
>
> The upshot from that thread was that by including a :session
> argument, you guarantee that the code runs on export.
>
> --Erik
>
> Andreas Leha wrote:
>> Hi all,
>>
>> I have severa
Hi all,
I am having trouble with LaTeX export (again). In my sample code, the
source block below the headline 'Plot' produces a correct pdf, when
evaluated (C-c C-c), but when exported, the pdf is broken.
(I am on commit 0f01b842bb2b6fada2579d0278fc53422e8ea62f since the
removal of htmlp prevent
tien:
> Hi Andreas,
>
> Andreas Leha writes:
>
>
>> #+BIND: org-export-latex-tables-centered nil
>> #+TITLE: Test Centered Tables
>>
>> * Test
>> | col1 | col2 | col3 |
>> |--+--+--|
>> |1 |2 |3 |
>
Hi all,
to make this explicit: I can not export to latex any more, but instead
I get
Exporting to LaTeX...
when: Symbol's value as variable is void: htmlp
Org HEAD
GNU emacs 23.2.1 (debian squeeze)
This is my failing org-file:
* Test
test
- Andreas
Am 16.02.2011 11:03, schrieb Bastien:
>
Hi all,
this topic has been here before and seems to be a TODO:
http://eschulte.github.com/babel-dev/TODO-shell-sessions-hang-in-many-cases.html
This still seems to be an issue
My questions:
(1) Has there been progress?
(2) Is there a better workaround than wrapping the shell commands in
another
Hi Piter,
First guess: functionality outside org-mode is slowing things down.
First candidate: line numbers turned on? If yes, try disabling.
Then there were discussions about speed here before, e.g.
http://www.mail-archive.com/[email protected]/msg27951.html
Maybe you find sth there.
HTH,
Hi all,
I usually produce tikz graphics in R which produce great results in
latex export (and I am able to handle them).
Now I have some plots too big to handle with tikz, so I go for pdf.
I have a question (example below):
There is one piece of code to produce several plots according to some
Hi all,
sorry to reopen this thread, but this does not work for me (GNU Emacs
23.2.1, Org almost HEAD c7700d7bbee4f7596feb199b1ec1bc7750d4fb48)
For me the image in the attached example is always created during
(LaTeX)export. Even if I do the manual evaluation once (and the hash is
created).
Th
style-include-scripts t
:style-include-default t :table-auto-headline t :tables t
:time-stamp-file t :creator-info t :email-info nil ...) nil nil)
org-export-as-latex(nil)
call-interactively(org-export-as-latex)
org-export(nil)
call-interactively(org-export nil nil)
Am 17.02.2011 11:5
Hi all experts,
When working with source code in org mode I like to keep the parameters
in org-tables. Especially since I have code in different languages that
should share the same set of parameters.
Problem is: When I tangle my source code blocks the tangled files loose
the parameters.
How do
Hi Jeffrey,
the attached sample file works for me.
The html is only sub-optimal, though, as it just includes a link to a
pdf file.
Cheers,
Andreas
Am 21.02.2011 02:56, schrieb Erik Iverson:
> Jeffrey,
>
>> Now, I'd like to integrate them into an org document. I'd like:
>> 1) To use babel to h
Can not reproduce this anymore. My variables are exported nicely now.
Sorry for the noise.
- Andreas
Am 21.02.2011 10:06, schrieb Sébastien Vauban:
> Hi Andreas,
>
> Andreas Leha wrote:
>
>> When working with source code in org mode I like to keep the parameter
Hi Torsten,
Have a look at the 'src_{}' construct as described here:
http://orgmode.org/org.html#Structure-of-code-blocks
Hth,
Andreas
Am 23.02.2011 06:55, schrieb Torsten Wagner:
> Hi,
>
> guess this is a FAQ or at least a stupid question.
> However, I read along worg and wasn't able to find a
a
> #+call aka #+lob aka #+function.
>
> I will try he src_python{print f} and use a session...
>
> However, I thought there might be a 'easier' way ;)
>
> Thanks
>
> Torsten
>
>
>
> On 02/23/2011 04:53 PM, Andreas Leha wrote:
>> Hi Torsten,
>&
Hi all,
Just a small patch that might make life easier for
LaTeX (and esp. tikz) users. It enables the output of graphics in a
lot of formats using imagemagick. See below for an example.
This is my first patch, I have never programmed emacs lisp before, and
my common lisp experiences have been
Hi all,
When ':noweb yes' is in the header, ':cache yes' is ignored during
export. (At least when I export the sample file below.)
To me this seems to be a bug. Or am I missing something?
Regards,
Andreas
PS: Example:
* Test
#+srcname: test_sleep
#+begin_src R :sessio
h as it changes over
> 10 lines -- which I'm pretty sure is the copyright assignment cutoff.
>
> For more information on contributing to Org-mode see the following
> http://orgmode.org/worg/org-contribute.html
>
> Thanks! -- Eric
>
> Andreas Leha writes:
>
>
&
le worked for me -- that is the results were returned
> without executing the "sleep 5" code.
>
> Maybe you are using an old version of Org, or you have non-standard
> default header argument values?
>
> Best -- Eric
>
> Andreas Leha writes:
>
>
>> Hi
Hi all,
I used to have parameters in org tables, which were in secions marked
with 'noexport'. Since this weekend, this does not work for me anymore.
Is this a bug or am I doing sth wrong here?
Regards,
Andreas
PS: the example (try to export)
* Parameters
be done with the
> `org-toggle-comment' command bound to C-c ;.
>
> Hope this helps -- Eric
>
> Andreas Leha writes:
>
>
>> Hi all,
>>
>> I used to have parameters in org tables, which were in secions marked
>> with 'noexport'. Since th
Thanks for the quick fix! Works nicely again!
Am 28.02.2011 20:32, schrieb Eric Schulte:
> Ah,
>
> This is a bug I introduced in one of my weekend commits. I've just
> pushed up a fix.
>
> Thanks for catching this -- Eric
>
> Andreas Leha writes:
>
>
>
Hi everyone,
Just pulled the latest HEAD and found that there is a regression in
babel. When a source block is evaluated via #+call the :results silent
header arguement is ignored during export
=test file
* Test1
#+srcname: test
#+begin_src R :session :exp
Hi,
there are two rather new "add-ons" to ess that -- when activated --
break the connection between the org document and a R-src-buffer:
auto-complete-mode for R:
http://www.emacswiki.org/emacs/AutoCompleteSources#toc2
yasnippet for R: http://www.svenhartenstein.de/Software/R-autoyas
As especial
; s.t. both of the tests in your example below export results.
>
> Best -- Eric
>
> Andreas Leha writes:
>
>
>> Hi everyone,
>>
>> Just pulled the latest HEAD and found that there is a regression in
>> babel. When a source block is
has no value, the
> following call line would be exported.
>
> #+call: test() :session *R* :exports none
>
> I just pushed up a fix which removes this requirement for named
> sessions, so you example below should now work.
>
> Best -- Eric
>
> Andreas Leha writes:
>
>
Hi all,
I have a feature request (if what I want is not already possible, that is).
Could a source code block, which has the :session header argument, be
associated with its session as soon as C-' is pressed?
The background to this question is, that all ess support functionality
for R (r-autoyas
ssion name)?
>
> With this information in hand it shouldn't be difficult to expand the
> C-' behavior for R s.t. it automatically associates the resulting
> Org-Src buffer with the proper R session.
>
> Good idea. Best -- Eric
>
> Andreas Leha writes:
>
>>
Hi Nicolas,
> As I announced in another thread, I'm starting a Beamer back-end for the
> new export engine. Though, before I start hacking, I have a question
> about environments.
Will this new backend support presentations in subtrees? I think, what
I want is not possible with the current one.
Hi suvayu ali,
> Hi Andreas,
>
> On Thu, Jun 28, 2012 at 12:40 PM, Andreas Leha
> wrote:
>> Will this new backend support presentations in subtrees? I think, what
>> I want is not possible with the current one.
>>
>> As an example, consider files structu
Hi all,
I am having trouble to find a way to set a short title for the exported
beamer document.
Illustration:
I'd like to see
,
| \title[short title]{long title}
`
in the exported latex document.
The first shot
,
| #+TITLE: [short title]{long title}
`
was too easy, I guess.
Hi all,
I am having problems with the export of a minimal org file:
,
| #+PROPERTY: session *R*
|
| * Test
|
| | dtrn | xgnd |
| |--+---|
| | engd | src_R[:exports results :results raw rep
Hi all,
there seems to be a bug in evaluating #+call lines.
To reproduce, consider this file:
,
| * Some Headline
| #+name: parameters
| #+BEGIN_SRC R
| ttt <- 1
| #+END_SRC
|
| * Some Other Headline
| #+call: parameters() :results silent :exports none
`
and do C-c C-c on the #+call: l
Hi Bastien and Sebastien,
thanks for taking this further!
"Sebastien Vauban"
writes:
> Hi Bastien,
>
> Bastien wrote:
>> Andreas Leha writes:
>>
>>> Overriding org's setting of \title with
>>> ,
>>> | #+TITLE:
Hi Eric,
Eric Schulte writes:
> Andreas Leha writes:
>
>> Hi all,
>>
>> I am having problems with the export of a minimal org file:
>>
>> ,
>> | #+PROPERTY: session *R*
&g
Bastien writes:
> Eric Schulte writes:
>
>> For some reason I am
>> currently unable to communicate with the Org-mode git server, so if
>> anyone else is able to apply this patch please do.
>
> Done - thanks for the patch!
Thanks for the patch and the check-in. I can confirm, that the issue is
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> I'd be a regular user of such functionality, especially for
>> presentations. But as the concept is useful in other (LaTeX-)
>> documents, a more general support for short titl
Hi all,
I started to get the error
: org-open-file: Symbol's function definition is void: org-e-latex-export-to-pdf
when trying to export to pdf in the new exporter. Any thought what
might be causing this?
I am using Org-mode version 7.8.11 (release_7.8.11-217-g99ef57) on emacs
24.1.50.1.
Tha
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> I started to get the error
>> : org-open-file: Symbol's function definition is void:
>> org-e-latex-export-to-pdf
>>
>> when trying to export to pdf in the new exporter. Any th
Hi all,
with the current HEAD (commit 0202adb1c02908a75a7845438381e40d811fd99a)
from master I get an error during the export of
one of my files complaining about an undefined my-filt function.
Replacing org-flet with flet in ob-comint.el (line 78) introduces a
compiler warning, but solves the pro
Eric Schulte writes:
> Andreas Leha writes:
>
>> Hi all,
>>
>> with the current HEAD (commit 0202adb1c02908a75a7845438381e40d811fd99a)
>> from master I get an error during the export of
>> one of my files complaining about an undefined my-filt function.
>
Eric Schulte writes:
> Andreas Leha writes:
>
>> Eric Schulte writes:
>>
>>> Andreas Leha writes:
>>>
>>>> Hi all,
>>>>
>>>> with the current HEAD (commit 0202adb1c02908a75a7845438381e40d811fd99a)
>>>> from
Bastien writes:
> Eric Schulte writes:
>
>> Regardless, I've just pushed up a fix which
>> replaces the named function with an anonymous lambda-expression. I've
>> also pushed up a test case which exercises this function. Everything
>> now seems to be working.
>
> Thanks!
Sorry for the late r
Hi all,
I started to get problems with commented latex headers. All headers
after the commented line seem to be ignored. Is this intended / am I
using the comments wrongly?
Test with new exporter - no cmbright:
,
| #+TITLE: Commented LaTeX headers
|
|
| * Try to export this subtree
| With
Hi Bastien,
thanks for looking into this!
>
> Please always tell what exporter you are using.
>
I did mention this:
> > Test with new exporter - no cmbright:
^^^
I am sorry, if this was not explicit enough. (Is "new exporter" the
correct name?)
> Your example works with
Hi Nicolas
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> I started to get problems with commented latex headers. All headers
>> after the commented line seem to be ignored. Is this intended / am I
>> using the comments wrongly?
>
> This
Hi all,
it seems to be not possible to follow references to images (for
example) as here:
There is a Figure [[fig_test_C_c_C_o]]
#+caption: Try to get to this figure via C-c C-o on the reference
#+label: fig_test_C_c_C_o
[[foo.png]]
I do not recall whether this has been possible at some time,
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> it seems to be not possible to follow references to images (for
>> example) as here:
>>
>> There is a Figure [[fig_test_C_c_C_o]]
>>
>> #+caption: Try to get to thi
Hi Bastien,
Bastien writes:
> Hi Andreas,
>
> Andreas Leha writes:
>
>> I experience a problem with the preview of latex fragments: I can not
>> change the foreground color (in org-format-latex-options). On a dark
>> background, the black fragments are barely
Hi all,
it seems to me, that #+call lines in subtrees with the :noexport: tag
are evaluated. Is this intended?
In my opinion, these #+calls should not be evaluated.
* Example
Export this subtree with org-export-dispatch. You will have to wait for
more than 1+10 secs...
** To be exported
This
Hi all,
I have the following question. Consider the following simple org file
#+begin_org
* Subtree to eval (with C-c C-v s)
#+name: some_test
#+begin_src R
5+1
#+end_src
* another subtree containing the result
#+results: some_test
: 6
#+end_org
(a)
When I evaluate the source block intera
Hi Sebastien,
"Sebastien Vauban"
writes:
> Hello Andreas,
>
> Andreas Leha wrote:
>> it seems to me, that #+call lines in subtrees with the :noexport: tag
>> are evaluated. Is this intended?
>
> I think that, at least, it's not a bug. I don't
Hi all,
is there a possibility to exclude (or include) parts of the document
based on some babel source block result?
First some use case:
Say, I am doing a statistical test. And only if the test turns out to be
significant, a follow-up analysis is carried out.
Is that possible?
One thinkable
Nicolas Goaziou writes:
> Hello,
>
> "Sebastien Vauban"
> writes:
>
>> Andreas Leha wrote:
>>> it seems to me, that #+call lines in subtrees with the :noexport: tag
>>> are evaluated. Is this intended?
>
> As far as the new exporte
Eric Schulte writes:
> "Sebastien Vauban" writes:
>
>> Hi Nicolas,
>>
>> Nicolas Goaziou wrote:
>>> "Sebastien Vauban" writes:
In fact, what you expect is that putting a tag ":noexport:" on a subtree
would
propagate the option ":eval no-export"[1] to all code blocks beneath it.
Eric Schulte writes:
> Andreas Leha writes:
>
>> Hi all,
>>
>> I have the following question. Consider the following simple org file
>>
>> #+begin_org
>> * Subtree to eval (with C-c C-v s)
>> #+name: some_test
>> #+begin_src R
>>
Eric Schulte writes:
> Andreas Leha writes:
>
>> Hi all,
>>
>> is there a possibility to exclude (or include) parts of the document
>> based on some babel source block result?
>>
>> First some use case:
>> Say, I am doing a statistical test. And
on. I have indeed done that already but I will
avoid such things in the future. It (a) feels wrong and (b) is ugly code
when I write (parts of) my document using print() and cat() functions.
Regards,
Andreas
>
> Andreas Leha writes:
>
>> Hi all,
>>
>> is there a po
Hi all,
by now I learned not to call behaviour not meeting my expectations a
bug hastily
So, here is my question:
Is it intended that code in commented lines gets executed during export?
# example: buggy, thus commented src_R{Sys.sleep(10) && stop("Here is a Bug")}
This kind of violates the
Hi all,
attached is a tiny patch for the new latex exporter that fixes a small
typo.
Regards,
Andreas
>From 0733a2a6882338a2fc507304069fa2ed12fdbf05 Mon Sep 17 00:00:00 2001
From: Andreas Leha
Date: Tue, 11 Sep 2012 09:33:45 +0200
Subject: [PATCH] fix typo in support of sidewaystables in
\usetheme{default}
\author{Andreas Leha}
\date{\today}
\title{Test Beamer}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Generated by Org mode 7.9.1 in Emacs 24.2.50.1.}}
\begin{document}
\maketitle
\begin{frame}{Outline}
\tableofcontents
\end{frame}
\begin{frame}[l
Hi Nicolas,
> Hello,
>
> Andreas Leha writes:
>
>> I am having trouble to export a subtree as beamer document with the new
>> exporter. (Org-mode version 7.9.1 (release_7.9.1-316-g66fe32)
>>
>> Here is a simple org-document, that was prepared for beamer
Hi Nicolas,
> Andreas Leha writes:
>
>> I was expecting a compilable Beamer document. Especially, I am missing
>> a document class in the exported TeX:
>>
>
> You need a "beamer" entry in `org-e-latex-classes' (note: "beamer" name
Hi Nicolas,
>> [ test_beamer.org ]
>> * Test Beamer
>>:PROPERTIES:
>>:EXPORT_LaTeX_CLASS: beamer
>>:EXPORT_LaTeX_CLASS_OPTIONS: [presentation]
>>:EXPORT_FILE_NAME: presentation.pdf
>>:COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act)
>> %4BEAMER_col(Col) %8BEAMER_op
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>>>> [ test_beamer.org ]
>>>> * Test Beamer
>>>>:PROPERTIES:
>>>>:EXPORT_LaTeX_CLASS: beamer
>>>>:EXPORT_LaTeX_CLASS_OPTIONS: [presentation
Hi all,
I am getting different results from the evaluation of a source block and
the evaluation of a #+call line to that block.
Therefore, my question: Is there an equivalent to
org-babel-expand-src-block (C-c C-v v) for #+call lines?
Or more general: How do I debug #+call lines?
Regards,
Andr
Hi all,
I am getting different results from the evaluation of a source block
itself and the evaluation of a #+call line to that block.
Therefore, here is my question: Is there an equivalent to
org-babel-expand-src-block (C-v C-v v) for call lines?
Or how should I debug a #+call line?
Regards,
A
Hi all,
(seems like I am having trouble to post -- sorry if multiple copies of
this end up on the list)
I am getting different results from the evaluation of a source block and
the evaluation of a #+call line to that block.
Therefore, my question: Is there an equivalent to
org-babel-expand-src-b
Hi Eric,
> Andreas Leha writes:
>
>> Hi all,
>>
>> I am getting different results from the evaluation of a source block and
>> the evaluation of a #+call line to that block.
>>
>> Therefore, my question: Is there an equivalent to
>> org-bab
Hi Eric,
> Andreas Leha writes:
>
>> Hi Eric,
>>
>>> Andreas Leha writes:
>>>
>>>> Hi all,
>>>>
>>>> I am getting different results from the evaluation of a source block and
>>>> the evaluation of a #+call line
Eric Schulte writes:
> Andreas Leha writes:
>
>> Hi Eric,
>>
>>
>>> Andreas Leha writes:
>>>
>>>> Hi Eric,
>>>>
>>>>> Andreas Leha writes:
>>>>>
>>>>>> Hi all,
>>>>>
Hi all,
is it possible to have babel add debugging lines during execution?
Consider this example with an enabled debug property:
#+PROPERTY: session *R*
#+PROPERTY: debug yes
* Some code blocks
#+name: codeA
#+begin_src R
sum(1)
#+end_src
#+name: codeB
#+begin_src R
sum(2)
#+end_src
When e
Hi all,
how is it possible to add an empty line to a LaTeX header?
Any empty
#+latex_header:
is 'stripped' from the exported document.
Background:
I am building a beamer presentation using the progress bar from
http://www.mrunix.de/forums/showpost.php?p=316577&postcount=3
and that definition re
Hi Sebastien,
"Sebastien Vauban"
writes:
> Hi Andreas,
>
> Andreas Leha wrote:
>> how is it possible to add an empty line to a LaTeX header?
>> Any empty
>> #+latex_header:
>> is 'stripped' from the exported document.
>
> Couldn
Hi Eric,
Eric S Fraga writes:
> Andreas Leha writes:
>
>> Hi all,
>>
>> how is it possible to add an empty line to a LaTeX header?
>> Any empty
>> #+latex_header:
>> is 'stripped' from the exported document.
>>
>>
>> Bac
Hi all,
I am not able to export a subtree, that has babel references pointing
outside, when I use the new exporter (it is working with the old one).
See the following example and export the second subtree only to
reproduce the problem:
---[ example orgmode file ]
#+TITLE: refs not in tree
#+LATE
Andreas Leha writes:
> Hi all,
>
> I am not able to export a subtree, that has babel references pointing
> outside, when I use the new exporter (it is working with the old one).
>
> See the following example and export the second subtree only to
> reproduce the problem:
>
Hi all,
I'd like to change the LaTeX header per subtree. Is that possible?
Use case: I have two documents that I want to export from a single
orgmode file. Each in its own subtree. One of them should use the
endfloat package, the other should not.
Like this:
,
| * Document 1
| #+LATEX_HE
1 - 100 of 690 matches
Mail list logo