From: James Harkins <jamshark70@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: "Emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>
Subject: Re: Exporting source code blocks as LaTeX figures
Date: Mon, 20 May 2013 15:00:53 +0800 [thread overview]
Message-ID: <CAFniQ7W96oN6HF3dVo2hMJgmaMbc+1d+MofjWfGYs78r-w5Nnw@mail.gmail.com> (raw)
In-Reply-To: <m1k3muduyy.fsf@tsdye.com>
On Mon, May 20, 2013 at 2:30 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>> Then the next problem... I'm going to have some figures that need to
>> span two columns. According to [1], I should use \begin{figure*} ...
>> \end{figure*}. Is there a way to do that using a special block? (First
>> guess, "#+BEGIN_figure*" causes the special block not to be
>> recognized.) Or do I need to write the literal LaTeX code for that?
>
> No, you don't need to write literal LaTeX code. See Section 12.7.4 of
> the manual, which describes setting the :float attribute to
> 'multicolumn'.
That section of the manual seems to describe the behavior for images. I did try:
#+ATTR_LaTeX: :multicolumn :options [htb]
#+BEGIN_figure
...
#+END_figure
... and :multicolumn had no effect on the output LaTeX code (either
with or without the preceding ":" -- I tried both):
\begin{figure}[htb]
\lstset{language={},label=code1,caption={Some code},numbers=none}
\begin{lstlisting}
// SuperCollider code here
.....
\end{lstlisting}
\end{figure}
Nor does this make a difference:
#+ATTR_LaTeX: :float multicolumn :options [htb]
#+BEGIN_figure
And if I omit BEGIN_figure altogether, and try to apply :float
directly to the source code block, then the floating environment
doesn't appear in the LaTeX code at all.
The other reference to multicolumn is for table export, and this isn't
a table either. So I think, as currently designed, :multicolumn simply
doesn't apply.
I'm aware that BEGIN_figure delimits a "special block" which
translates into LaTeX as an arbitrary environment, and not all
environments can be floated safely... but perhaps one approach for the
future would be to consider BEGIN_figure to be an extra-special
"special block" where we know that the properties of LaTeX floating
bodies are valid.
Or relax the restriction so that BEGIN_figure* no longer tries to
treat _ as a subscript marker.
hjh
next prev parent reply other threads:[~2013-05-20 7:01 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
2013-05-20 4:06 ` James Harkins
2013-05-20 6:30 ` Thomas S. Dye
2013-05-20 7:00 ` James Harkins [this message]
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=CAFniQ7W96oN6HF3dVo2hMJgmaMbc+1d+MofjWfGYs78r-w5Nnw@mail.gmail.com \
--to=jamshark70@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--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).