Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
A better place would be the line below planning info, if any, or below
the headline otherwise.
Yes, exactly.
--
Bastien
Hello,
Bastien b...@gnu.org writes:
Well, we can poll users and see how inconvenient this change would be.
(I'm certainly biased here, as I never use blank lines between the
headline and the properties drawer.)
Blank lines between the headline and the properties drawer is not
enough,
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Maybe it's time to forbid blank lines between headlines and the
properties drawer? Or at least to discourage separating them in
the manual? Otherwise I don't have a steady solution at hand.
I think this is fixed already.
Okay,
Hello,
Bastien b...@gnu.org writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Maybe it's time to forbid blank lines between headlines and the
properties drawer? Or at least to discourage separating them in
the manual? Otherwise I don't have a steady solution at hand.
I think this
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
As a side note, forbidding blank lines between headlines and the
properties drawer (or better just after the planning line, if any) would
make parsing easier and faster in a lot of cases. Unfortunately, I think
this would break a
Bastien wrote:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
As a side note, forbidding blank lines between headlines and the
properties drawer (or better just after the planning line, if any) would
make parsing easier and faster in a lot of cases. Unfortunately, I think
this would break
Hi Sébastien,
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
the frame inherits from the property BEAMER_opt which, though, is only
present in the example code, not in the Beamer frame itself.
Maybe it's time to forbid blank lines between headlines and the
Hello,
Bastien b...@gnu.org writes:
Maybe it's time to forbid blank lines between headlines and the
properties drawer? Or at least to discourage separating them in
the manual? Otherwise I don't have a steady solution at hand.
I think this is fixed already.
Regards,
--
Nicolas Goaziou
Hello,
When having such a code block inside a frame:
--8---cut here---start-8---
#+TITLE: Org Beamer examples
#+LANGUAGE: en
#+OPTIONS: H:2 num:nil ^:{}
#+PROPERTY: eval no
#+LATEX_HEADER: \lstdefinelanguage{org}{}
* ECM
** Allow frame breaks
In
Hello,
When having such a code block inside a frame, the frame inherits
from the property BEAMER_opt which, though, is only present in the
example code, not in the Beamer frame itself.
Another example which is not compilable in LaTeX (because of that bug):
--8---cut
10 matches
Mail list logo
