Hi Nicolas,
Nicolas Goaziou writes:
> A better place would be the line below planning info, if any, or below
> the headline otherwise.
Yes, exactly.
--
Bastien
Hello,
Bastien 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, because you s
Bastien wrote:
> Nicolas Goaziou 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 lot of fi
Hi Nicolas,
Nicolas Goaziou 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 lot of files, too.
Hello,
Bastien writes:
> Nicolas Goaziou 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.
>
Hi Nicolas,
Nicolas Goaziou 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, I didn't see an
Hello,
Bastien 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
Hi Sébastien,
Sebastien Vauban
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
properties drawer? Or at least to discourage separa
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 here
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 y
10 matches
Mail list logo
