emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: [Latex] Don't push code blocks to end of document (was: Source blocks with captions)
Date: Wed, 25 Jun 2014 13:20:51 +0200	[thread overview]
Message-ID: <87tx79kzfw.fsf_-_@mailbox.org> (raw)
In-Reply-To: <87pphymqts.fsf@mailbox.org> (Alexander Baier's message of "Tue, 24 Jun 2014 14:31:43 +0200")

On 2014-06-24 14:31 Alexander Baier wrote:

[...]

>> 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?

In fact, the document class does not drop those captions, it just moves
the listings to the end of the document, where I did not see them.

How do I prevent this from happening? It is not much use to me if _all_
my listings are pushed to the very end of my document. I would like
latex to place them in the vicinity of where I defined my code block in
org.

This is the test file showing the behaviour described above:

----------------------------------------------------------------
#+LANGUAGE: de
#+OPTIONS: tasks:nil num:3 toc:nil ':t ":t
#+LATEX_CLASS: llncs
#+TITLE: Test

* A headline
Some words before the source code block.
For good measure, here is a link to listing [[src:foo]].

#+NAME: src:foo
#+CAPTION: test caption.
#+BEGIN_SRC java
  interface Foo {
      void bar();
  }
#+END_SRC

And some words after the block.
----------------------------------------------------------------


Thanks,
-- 
Alexander Baier

  reply	other threads:[~2014-06-25 11:21 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
2014-06-25 11:20         ` Alexander Baier [this message]
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=87tx79kzfw.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).