From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [beamer] Code blocks in lists?
Date: Tue, 07 Feb 2012 23:39:31 +0100 [thread overview]
Message-ID: <808vke9skc.fsf@somewhere.org> (raw)
In-Reply-To: 87sjinude1.fsf@gmail.com
Hi Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban"
> <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> Nicolas Goaziou wrote:
>>> "Sebastien Vauban" writes:
>>>
>>>> I've identified a couple of troubles related to code blocks inside lists (in
>>>> Beamer):
>>>>
>>>> - code blocks break the list
>>>>
>>>> - "relative" indentation of the code inside its frame is wrong except when
>>>> code begins at column 0: is this a requirement?
>>>>
>>>> - sometimes, "ORG-LIST-END-MARKER" is exported in PDF and in HTML.
>>>
>>> Could you try with a more recent Org? I think I have fixed this
>>> recently.
>>
>> I confirm that those 3 bugs (?) are there in the "release of this
>> hour":
>
> I can't reproduce any list break ...
Does that mean that you consider the following as normal?
#+begin_src latex
\begin{frame}[fragile]
\frametitle{Code in lists}
\framesubtitle{Correct Org syntax}
\label{sec-1}
\begin{itemize}
\item This is an item
This is some text to show how it's aligned\ldots{}
This is some extra text\ldots{}
\item This code block is properly indented in Org
\end{itemize}
\lstset{language=java}
\begin{lstlisting}
if (test)
{
doit
}
\end{lstlisting}
but \textbf{no correct relative indentation} in both PDF and HTML: see the code
within its frame. There is a \emph{left margin} appended, not intended. Do I have
to begin \textbf{all code blocks in column 0}?
ORG-LIST-END-MARKER
\end{frame}
#+end_src
You see that there are 2 items in the list, which is ended, then there is the
code, then some "volatile" paragraph.
In the PDF, the paragraph "but ..." is not indented properly, as it would have
been if the code wasn't there, in the middle.
> ... except the last one, which is on purpose (block at column 0).
IIUC, every code block, inside lists or not, must be located at column 0?
>> Org-mode version 7.8.03 (release_7.8.03.356.gfe2e)
>
> Strange. This version doesn't exist yet. As the time of writing, we're
> at release: Org-mode version 7.8.03 (release_7.8.03.321.gaac1c).
I have no idea why it's the case: I don't have any pending modification or
whatsoever, and simply git pull every day or so. Though, my Git experience is
still limited...
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-02-07 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 12:58 [beamer] Code blocks in lists? Sebastien Vauban
2012-02-06 13:11 ` Nicolas Goaziou
2012-02-06 16:07 ` Sebastien Vauban
2012-02-06 16:37 ` Nicolas Goaziou
2012-02-07 22:39 ` Sebastien Vauban [this message]
2012-02-07 23:21 ` Nick Dokos
2012-02-09 16:34 ` Nicolas Goaziou
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=808vke9skc.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).