From: "Thomas S. Dye" <tsd@tsdye.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: latex export of source code in lists
Date: Thu, 9 Dec 2010 15:29:01 -1000 [thread overview]
Message-ID: <AAC79D71-2A90-4500-A6AD-E1C581A43FA6@tsdye.com> (raw)
In-Reply-To: <4D01162B.4060207@med.uni-goettingen.de>
Aloha Andreas,
I gather Nicolas Goaziou has worked some magic so that your example
works with lists now.
I had problems using the listings package in situations where LaTeX
changes \linewidth, as it can do inside lists. I got bad line breaks
and wasn't able to make them good. If listings works for you in this
kind of environment, please let me know how you got it to work.
All the best,
Tom
On Dec 9, 2010, at 7:47 AM, Andreas Leha wrote:
> Hi Tom,
>
> thanks for all your input! This is great.
>
> Using a float environment around my listings is an option I have not
> considered yet, as I have a lot of code snippets in the one file,
> which
> would result in several pages of floating listings. But I'll use that
> option anyway or do completely without lists then.
>
> Thanks again,
> Andreas
>
>
>
> Am 09.12.2010 18:25, schrieb Thomas S. Dye:
>> Hi Andreas,
>>
>> In my experience, lists are a bit fragile this way (probably
>> necessarily). One workaround might be to float the source code block
>> (in the way I mentioned in a previous message) and then cross
>> reference it from the list.
>>
>> * Test
>> 1) this is the first item (Listing \ref{fig:first-code})
>> 2) this is the second item (Listing \ref{fig:second-code})
>>
>> But this might not be what you're after.
>>
>> All the best,
>> Tom
>>
>> On Dec 8, 2010, at 11:38 PM, Andreas Leha wrote:
>>
>>> Hi all,
>>>
>>> (how) can I have source code block in lists not breaking the latex
>>> exported list?
>>>
>>> Example:
>>> * Test
>>> 1) this is the first item
>>> #+srcname: code
>>> #+begin_src R :tangle no :export code
>>> print("some code")
>>> #+end_src
>>> which has some code
>>>
>>> 2) this is the second item
>>>
>>> This results in
>>> \section{Test}
>>> \label{sec-1}
>>>
>>> \begin{enumerate}
>>> \item this is the first item
>>> \end{enumerate}
>>>
>>> \lstset{language=R}
>>> \begin{lstlisting}
>>> print("some code")
>>> \end{lstlisting}
>>> which has some code
>>>
>>> \begin{enumerate}
>>> \item this is the second item
>>> \end{enumerate}
>>>
>>> While I expect this:
>>> \section{Test}
>>> \label{sec-1}
>>>
>>> \begin{enumerate}
>>> \item this is the first item
>>> \lstset{language=R}
>>> \begin{lstlisting}
>>> print("some code")
>>> \end{lstlisting}
>>> which has some code
>>>
>>> \item this is the second item
>>> \end{enumerate}
>>>
>>> Thanks,
>>> Andreas
>>>
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Please use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>
> --
> Andreas Leha
>
> Universitätsmedizin Göttingen
> Abteilung Medizinische Statistik
> Humboldtallee 32
> 37073 Göttingen
>
> Tel: +49 (0)551 39-10710
> Fax: +49 (0)551 39-4995
>
> http://www.ams.med.uni-goettingen.de/amsneu/leha.html
>
>
>
> University Medical Center Göttingen
> Department for Medical Statistics
> Humboldtallee 32
> 37073 Göttingen
> Germany
>
> Phone: +49 (0) 551 39-10710
> Fax: +49 (0) 551 39-4995
>
> http://www.ams.med.uni-goettingen.de/amsneu/leha-en.html
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-12-10 1:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 9:38 latex export of source code in lists Andreas Leha
2010-12-09 17:25 ` Thomas S. Dye
2010-12-09 17:47 ` Andreas Leha
2010-12-10 1:29 ` Thomas S. Dye [this message]
2010-12-09 20:36 ` Nicolas Goaziou
2010-12-10 17:01 ` Andreas Leha
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=AAC79D71-2A90-4500-A6AD-E1C581A43FA6@tsdye.com \
--to=tsd@tsdye.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
/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).