* LaTeX export with listings: multicolumn support broken?
@ 2013-12-11 14:54 James Harkins
2013-12-11 15:02 ` Nicolas Goaziou
2013-12-11 15:03 ` James Harkins
0 siblings, 2 replies; 7+ messages in thread
From: James Harkins @ 2013-12-11 14:54 UTC (permalink / raw)
To: orgmode
A few months ago, I wrote an academic paper with code examples, using the
listings environment like so:
#+ATTR_LaTeX: :starred t :options [htb]
#+BEGIN_figure
#+CAPTION: Simple sequencer, implementing the musical flow from Figure
[[basicseq_graph]].
#+NAME: basicseq
#+BEGIN_SRC {} -i
TLSequenceIterator([
bpCmd: (name: \rumble, dur: 40),
15,
bpCmd: (name: \whine, dur: 20)
]);
#+END_SRC
#+END_figure
Now I need to submit revisions for the same paper, and ":starred t" is
ignored. I get \begin{figure}, not \begin{figure*} as before.
I have also tried
#+ATTR_LaTeX: :float multicolumn :options [htb]
per documentation at [1]. I still get \begin{figure}, not \begin{figure*}.
What happened?
My paper is due on Sunday (Dec. 15). Need a fix fairly soon. If nothing
else, I will downgrade via git.
hjh
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: LaTeX export with listings: multicolumn support broken?
2013-12-11 14:54 LaTeX export with listings: multicolumn support broken? James Harkins
@ 2013-12-11 15:02 ` Nicolas Goaziou
2013-12-11 15:16 ` James Harkins
2013-12-11 15:03 ` James Harkins
1 sibling, 1 reply; 7+ messages in thread
From: Nicolas Goaziou @ 2013-12-11 15:02 UTC (permalink / raw)
To: James Harkins; +Cc: orgmode
Hello,
James Harkins <jamshark70@gmail.com> writes:
> A few months ago, I wrote an academic paper with code examples, using the
> listings environment like so:
>
> #+ATTR_LaTeX: :starred t :options [htb]
> #+BEGIN_figure
> #+CAPTION: Simple sequencer, implementing the musical flow from Figure
> [[basicseq_graph]].
> #+NAME: basicseq
> #+BEGIN_SRC {} -i
> TLSequenceIterator([
> bpCmd: (name: \rumble, dur: 40),
> 15,
> bpCmd: (name: \whine, dur: 20)
> ]);
> #+END_SRC
> #+END_figure
>
> Now I need to submit revisions for the same paper, and ":starred t" is
> ignored. I get \begin{figure}, not \begin{figure*} as before.
>
> I have also tried
>
> #+ATTR_LaTeX: :float multicolumn :options [htb]
>
> per documentation at [1]. I still get \begin{figure}, not \begin{figure*}.
>
> What happened?
I could be a suggested feature that didn't make it into code base.
Anyway, you can use:
#+begin_figure*
...
#+end_figure*
instead.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: LaTeX export with listings: multicolumn support broken?
2013-12-11 14:54 LaTeX export with listings: multicolumn support broken? James Harkins
2013-12-11 15:02 ` Nicolas Goaziou
@ 2013-12-11 15:03 ` James Harkins
2013-12-11 15:22 ` Nicolas Goaziou
1 sibling, 1 reply; 7+ messages in thread
From: James Harkins @ 2013-12-11 15:03 UTC (permalink / raw)
To: orgmode
On Wednesday, December 11, 2013 10:54:37 PM HKT, James Harkins wrote:
> I have also tried
>
> #+ATTR_LaTeX: :float multicolumn :options [htb]
>
> per documentation at [1]. I still get \begin{figure}, not
\begin{figure*}.
Forgot the footnote: it's
http://orgmode.org/manual/LaTeX-specific-attributes.html#LaTeX-specific-attributes
Anyway, I've tested 8.2, 8.1.2, 8.1.0 and a previous "sandbox" branch I
used at some point in the past. None of them give me multicolumn figures
for code blocks.
Well, certainly it worked back in August...
hjh
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: LaTeX export with listings: multicolumn support broken?
2013-12-11 15:02 ` Nicolas Goaziou
@ 2013-12-11 15:16 ` James Harkins
0 siblings, 0 replies; 7+ messages in thread
From: James Harkins @ 2013-12-11 15:16 UTC (permalink / raw)
To: emacs-orgmode
Nicolas Goaziou <n.goaziou <at> gmail.com> writes:
> I could be a suggested feature that didn't make it into code base.
> Anyway, you can use:
>
> #+begin_figure*
> ...
> #+end_figure*
>
> instead.
OK, relief. That did it.
Should #+begin_something* be documented under "special blocks" here?
http://orgmode.org/manual/LaTeX-specific-attributes.html#LaTeX-specific-attributes
hjh
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: LaTeX export with listings: multicolumn support broken?
2013-12-11 15:03 ` James Harkins
@ 2013-12-11 15:22 ` Nicolas Goaziou
2013-12-12 6:59 ` James Harkins
0 siblings, 1 reply; 7+ messages in thread
From: Nicolas Goaziou @ 2013-12-11 15:22 UTC (permalink / raw)
To: James Harkins; +Cc: orgmode
James Harkins <jamshark70@gmail.com> writes:
> On Wednesday, December 11, 2013 10:54:37 PM HKT, James Harkins wrote:
>> I have also tried
>>
>> #+ATTR_LaTeX: :float multicolumn :options [htb]
>>
>> per documentation at [1]. I still get \begin{figure}, not
> \begin{figure*}.
>
> Forgot the footnote: it's
> http://orgmode.org/manual/LaTeX-specific-attributes.html#LaTeX-specific-attributes
>
> Anyway, I've tested 8.2, 8.1.2, 8.1.0 and a previous "sandbox" branch
> I used at some point in the past. None of them give me multicolumn
> figures for code blocks.
>
> Well, certainly it worked back in August...
Your first "attr_latex" line applies to the "figure" special block, not
to the source block.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: LaTeX export with listings: multicolumn support broken?
2013-12-11 15:22 ` Nicolas Goaziou
@ 2013-12-12 6:59 ` James Harkins
2013-12-12 17:35 ` Nicolas Goaziou
0 siblings, 1 reply; 7+ messages in thread
From: James Harkins @ 2013-12-12 6:59 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: orgmode
On Wed, Dec 11, 2013 at 11:22 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Your first "attr_latex" line applies to the "figure" special block, not
> to the source block.
I did eventually figure that out.
As far as I can see, this is the only reference to figure*
environments in the manual:
~~
multicolumn: if you wish to include an image which spans multiple
columns in a page. This will export the image wrapped in a figure*
environment.
~~
It's a reasonable (though wrong) conclusion from this that
"multicolumn" is /the/ way to get figure*.
I think it would be worth noting in the "Special blocks in LaTeX
export" section that * is valid as a character in special block
identifiers.
hjh
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: LaTeX export with listings: multicolumn support broken?
2013-12-12 6:59 ` James Harkins
@ 2013-12-12 17:35 ` Nicolas Goaziou
0 siblings, 0 replies; 7+ messages in thread
From: Nicolas Goaziou @ 2013-12-12 17:35 UTC (permalink / raw)
To: jamshark70; +Cc: orgmode
Hello,
James Harkins <jamshark70@gmail.com> writes:
> On Wed, Dec 11, 2013 at 11:22 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>> Your first "attr_latex" line applies to the "figure" special block, not
>> to the source block.
>
> I did eventually figure that out.
>
> As far as I can see, this is the only reference to figure*
> environments in the manual:
>
> ~~
> multicolumn: if you wish to include an image which spans multiple
> columns in a page. This will export the image wrapped in a figure*
> environment.
> ~~
>
> It's a reasonable (though wrong) conclusion from this that
> "multicolumn" is /the/ way to get figure*.
It is /the/ way for images.
> I think it would be worth noting in the "Special blocks in LaTeX
> export" section that * is valid as a character in special block
> identifiers.
That, or provide an example that uses such a special block. Do you want
to provide a patch?
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2013-12-12 17:35 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-12-11 14:54 LaTeX export with listings: multicolumn support broken? James Harkins
2013-12-11 15:02 ` Nicolas Goaziou
2013-12-11 15:16 ` James Harkins
2013-12-11 15:03 ` James Harkins
2013-12-11 15:22 ` Nicolas Goaziou
2013-12-12 6:59 ` James Harkins
2013-12-12 17:35 ` Nicolas Goaziou
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).