From: Alexander Baier <alexander.baier@mailbox.org>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode@gnu.org, Thorsten Jolitz <tjolitz@gmail.com>
Subject: Re: Source blocks with captions
Date: Tue, 24 Jun 2014 14:31:43 +0200 [thread overview]
Message-ID: <87pphymqts.fsf@mailbox.org> (raw)
In-Reply-To: <m238evsa5b.fsf@tsdye.com> (Thomas S. Dye's message of "Mon, 23 Jun 2014 09:23:12 -1000")
On 2014-06-23 21:23 Thomas S. Dye wrote:
> Aloha Alexander,
>
> Alexander Baier <alexander.baier@mailbox.org> writes:
>
>> On 2014-06-23 17:43 Thorsten Jolitz wrote:
>>> Alexander Baier <alexander.baier@mailbox.org> writes:
>>>
>>>> Hello org-moders!
>>>>
>>>> I just tried to put a caption under/on/above (or anywhere for that
>>>> matter) my source code block. When exporting to latex, I didn't see any
>>>> caption belonging to my code block. Other backends have not been
>>>> tried. How can I achieve this?
>>>>
>>>> For reference, I run Org-mode version 8.2.6 (release_8.2.6 @
>>>> /home/delexi/.emacs.d/ext/org-mode/lisp/) and this is the org file:
>>>>
>>>> * Test
>>>> #+CAPTION: Test
>>>> #BEGIN_SRC java
>>>> // some code
>>>> #END_SRC
>>>
>>> shouldn't that be
>>>
>>> ,----
>>> | #+NAME: Test
>>> `----
>>>
>>> instead of
>>>
>>> ,----
>>> | #+CAPTION: Test
>>> `----
>>>
>>> ?
>>
>> This does not work for me - I still see no caption or a similar thing in
>> the vicinity of my code block. Does "#+NAME" work for you?
>>
>> Regards,
>
> There are two errors in your Org mode file on the BEGIN_SRC and END_SRC
> lines.
You are of course right! This was just a mistake I made whilst putting
together this short example. In my "normal" setup the source code
blocks have the right form.
> With this code:
>
> * Test
>
> #+CAPTION: Test
> #+BEGIN_SRC java
> // some code
> #+END_SRC
>
> I get a figure with a caption when exporting to LaTeX:
>
> \section{Test}
> \label{sec-1}
>
> \begin{figure}[H]
> \begin{verbatim}
> // some code
> \end{verbatim}\caption{Test}
>
> \end{figure}
>
> You don't need to name the source code block, although it is typically a
> good idea to do so.
I always only looked at the generated PDF to see if there was a caption
added. When opening the generated .tex file I found the same code you
are seeing. It seems the document class I am using just drops the
caption.
The class in question is LLNCS, does anyone know why this could happen?
Regards,
--
Alexander Baier
next prev parent reply other threads:[~2014-06-24 12:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 15:19 Source blocks with captions Alexander Baier
2014-06-23 15:43 ` Thorsten Jolitz
2014-06-23 18:47 ` Alexander Baier
2014-06-23 19:23 ` Thomas S. Dye
2014-06-24 12:31 ` Alexander Baier [this message]
2014-06-25 11:20 ` [Latex] Don't push code blocks to end of document (was: Source blocks with captions) Alexander Baier
2014-06-25 12:22 ` [Latex] Don't push code blocks to end of document Alexander Baier
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=87pphymqts.fsf@mailbox.org \
--to=alexander.baier@mailbox.org \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@gmail.com \
--cc=tsd@tsdye.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).