Re: [O] [bug, beamer] Frame parameters taken from example code block
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
Re: [O] [bug, beamer] Frame parameters taken from example code block
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, because you still have to `re-search-forward', possibly far away from the headline. A better place would be the line below planning info, if any, or below the headline otherwise. Regards, -- Nicolas Goaziou
Re: [O] [bug, beamer] Frame parameters taken from example code block
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, I didn't see any confirmation on the mailing list. Thanks, -- Bastien
Re: [O] [bug, beamer] Frame parameters taken from example code block
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 is fixed already. Okay, I didn't see any confirmation on the mailing list. I probably forgot to confirm it. See ab145f0df553e0bb77795c946ff158d8c069f6e4 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. Regards, -- Nicolas Goaziou0x80A93738
Re: [O] [bug, beamer] Frame parameters taken from example code block
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 lot of files, too. 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.) If it's not too inconvenient, we can plan this for Org 9.0. -- Bastien
Re: [O] [bug, beamer] Frame parameters taken from example code block
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 a lot of files, too. 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.) If it's not too inconvenient, we can plan this for Org 9.0. Sorry for taking too much time to answer, but I'm under constant flood here, because of holiday times and the such. First, please note I wouldn't flag the bug as being caused by a property drawer detached from the headline. For me, the problem (in the ECM I gave) is interpreting the contents of the Org code block (in the given case: an headline with a property drawer following it). I regard that interpretation of what's inside the Org code block as the real cause of the problem. Maybe interpretation is not the right term, but the code block should never be allowed to be scanned when searching properties of the current headline IMHO. Second, I neither never ever have property drawers separated from headlines. I think that could be safely enforce, anyway, as all the tools in Org (C-c C-x p, C-c C-x C-i, C-c C-s, C-c C-d, etc.) never make such a case appear. Best regards, Seb -- Sebastien Vauban
Re: [O] [bug, beamer] Frame parameters taken from example code block
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 properties drawer? Or at least to discourage separating them in the manual? Otherwise I don't have a steady solution at hand. Best, -- Bastien
Re: [O] [bug, beamer] Frame parameters taken from example code block
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
[O] [bug, beamer] Frame parameters taken from example code block
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 your Org file, writing a code such as:
#+begin_src org :eval no
,** A very long frame with breaks
:PROPERTIES:
:BEAMER_opt: allowframebreaks,label=
:END:
#+end_src
will make that frame over multiple slides, as needed.
--8---cut here---end---8---
the frame inherits from the property BEAMER_opt which, though, is only
present in the example code, not in the Beamer frame itself.
See http://screencast.com/t/fc3pNAXTAhK4.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [bug, beamer] Frame parameters taken from example code block
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---start-8---
#+TITLE: Org Beamer examples
#+LANGUAGE: en
#+OPTIONS: H:2 num:nil ^:{}
#+PROPERTY: eval no
#+LATEX_HEADER: \lstdefinelanguage{org}{}
* ECM
** ~beamercolorbox~ environment
In your Org file, writing this:
#+begin_src org
,#+LaTeX: \setbeamercolor{mycolor}{bg=green,fg=white}
,*** mycolor :B_beamercolorbox:
:PROPERTIES:
:BEAMER_env: beamercolorbox
:BEAMER_opt: wd=6cm
:END:
Lorem ipsum...
#+end_src
displays a green post-it with a width of 6 cm.
--8---cut here---end---8---
See http://screencast.com/t/PY4nFxcKHe.
Best regards,
Seb
--
Sebastien Vauban
