From: Nicolas Goaziou <n.goaziou@gmail.com>
To: jamshark70@dewdrop-world.net
Cc: "Emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>
Subject: Re: Exporting source code blocks as LaTeX figures
Date: Sat, 18 May 2013 09:39:49 +0200 [thread overview]
Message-ID: <87r4h4ohx6.fsf@gmail.com> (raw)
In-Reply-To: <CAFniQ7XoK+kBn66KGh-gRU41oCuchKgJQoJAO+QhMVbHTHn3Hw@mail.gmail.com> (James Harkins's message of "Fri, 17 May 2013 15:14:21 +0800")
Hello,
James Harkins <jamshark70@gmail.com> writes:
> Couple of questions about exporting LaTeX figures that are neither
> tables nor images -- specifically, source code blocks using the
> listings package.
>
> 1. Is there any way to use #+CAPTION with a #+BEGIN_figure block, so
> that the caption will be rendered underneath the text in the figure?
>
> It seems (from reading the org manual and some experimentation on my
> own) that the answer is no. That's rather inconvenient; the journal
> specifies that captions should appear below their respective figures,
> but as it is:
>
> #+CAPTION: Some code
> #+NAME: code1
> #+BEGIN_figure
> #+BEGIN_SRC {}
> // blah blah
Why don't you use:
#+begin_figure
#+caption: Some code
#+name: code1
#+begin_src {}
// blah blah
instead? I.e., why don't you apply caption to src block? You can tweak
the position of the caption with "captionpos" option in listings
environment.
Caption are not supported in special blocks because these could contain
more than one object, and it wouldn't be clear which of them would have
the caption.
> 2. Is the customize variable "Org Latex Default Figure Position" only
> used for tables and images? It would be nice if it applied to
> BEGIN_figure as well (unless :options override that). "#+ATTR_LaTeX:
> :options [htb]" is a mite inconvenient to replicate for every code
> example. Certainly possible, but it would save a little effort if the
> default were used here too.
BEGIN_figure is a "special block", i.e. a generic environment. "[htb]"
does not always make sense in every environment.
Also, figure environment is created automatically in some cases (e.g.,
when `org-latex-listings' is nil and source block is captioned), so you
generally don't need to write it explicitly.
Anyway, you can easily add "[htb]" options to all figure environments in
the output with a filter.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-05-18 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 7:14 Exporting source code blocks as LaTeX figures James Harkins
2013-05-18 7:39 ` Nicolas Goaziou [this message]
2013-05-20 4:06 ` James Harkins
2013-05-20 6:30 ` Thomas S. Dye
2013-05-20 7:00 ` James Harkins
2013-05-20 8:54 ` Nicolas Goaziou
2013-05-21 0:13 ` James Harkins
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=87r4h4ohx6.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
/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).