emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] issues with export of LaTeX figure captions


From: Sebastien Vauban
Subject: Re: [O] issues with export of LaTeX figure captions
Date: Mon, 06 May 2013 14:11:46 +0200
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (windows-nt)

Hi RJ,

RJ Cunningham wrote:
> "Sebastien Vauban" <address@hidden> writes:
>> RJ Cunningham wrote:
>>> I've encountered an issue/difference with the way the recent "babel
>>> processor" handles captions.
>>>
>>> In versions prior to 8 the following WORKED (on export produced a figure
>>> environment with a caption):
>>>
>>> #+CAPTION: Fails to produce table environment and so caption in the new 
>>> orgmode
>>> #+LABEL: fig:fails
>>> #+begin_src R :session :results graphics :file fails.pdf :exports results
>>> plot(1:10)
>>> #+end_src
>>
>> Side-remark: I find it weird, if not uncorrect, to have the header argument
>> ":session" empty. IIRC, this is, at best, dangerous, because it could
>> interpret what follows as its value.
>
> I guess it could be dangerous, though it is convenient and I don't
> believe it has ever caused me any issues. I note that at one time, at
> least, a name was an optional argument for the :session header (see
> http://www.jstatsoft.org/v46/i03/paper p 10). I will consider being less
> weird though as you suggest.

It never occurred to me that there could be a default name (see
http://orgmode.org/manual/session.html#session), but OK, maybe. Anyway, I told
you that because I once had the problem of the following header arg eaten as
the option given to the previous one, though not with ":session".

>>> Under orgmode version 8.0.2 (8.0.2-2-g93da18-elpa the same code does
>>> not work, the includegraphics is exported sans the figure environment.
>>>
>>> Under this latest orgmode the following does work:
>>>
>>> #+begin_src R :session :results graphics :file ok.pdf :exports results
>>> plot(1:10)
>>> #+end_src
>>> #+CAPTION: Succeeds to produce table environment and so caption
>>> #+LABEL: fig:OK
>>> #+RESULTS[2d39a23f088d95e808bb867f97a0ecd2df621bbd]:
>>> [[file:ok.pdf]]
>>>
>>> However, this second construction of code has the following issues [...]:
>>>  2. it is ugly to have the caption sandwiched between the code and the
>>>  results
>>
>> Not really. Please well think that there are two different beasts here: the
>> code block and the results block. You can export both, and you could attach
>> (different) captions to both. So, that does not seems that illogical to me.
>
> OK, that is not something I have ever needed but I see that it would
> make sense in such a situation.

We do agree.

> Is there any way that I can export figures with captions WITHOUT having to
> execute the code and capture the results in the org file.

Once again, some question I never asked myself, always wanting to see at least
as much as what will be exported. But I understand your question, and a
possible good reason therefore (when the results is huge).

> With the previous construction the caption was added to the executed code
> results on export-so reducing the clutter in the org file by not having the
> results in the org file.

Honestly, I don't know. I would have the impression that you can't, but I may
be totally mislead...

>>>  3. often, but not always, when the code is re-executed the caption and
>>>  label is lost
>>
>> Can you provide an ECM for this?
>
> The problem seems to relate to :cache
>
> This gobbles up the caption and label.

If you did not execute the code block previously. Once pre-evaluated, your bug
does not appear anymore -- that does not mean it's not a problem, though.

> #+begin_src R :session :results graphics :file ok.pdf :exports results :cache 
> yes
> plot(1:10, col="blue",cex=1)
> #+end_src
> #+CAPTION: Succeeds to produce table environment and so caption XXXX
> #+LABEL: fig:OK
> #+RESULTS:
> [[file:ok.pdf]]
>
> :cache no is fine

I don't have time right now to further try to understand and help you, but it
really is strange. I confirm your saying about with or without cache, but had
other strange behaviors trying to export (only one fig got exported when I had
the two blocks).

I can't commit on when, but I'll also try to better understand what happens
here. Maybe others (Eric, Nicolas, Achim...) will come earlier with hints
about this.

Best regards,
  Seb

-- 
Sebastien Vauban




reply via email to

[Prev in Thread] Current Thread [Next in Thread]