New beamer support

New beamer support

[Sébastien Vauban]

Hello all,

Here a few comments, after my first attempt with the new beamer support --
excellent, needless to say...

Before that, I was using Nick's export class. But, now, I'm using yesterday's
git version.

The few things I'm tackling right now are:

- How to get a TOC with a frame title, without having to add it explicitly?

- How to get alerted text, without customizing `org-export-emphasis-alist'?
  Has this been forgotten from the commit?

- How to get "frame breaks", without modifying the resulting TeX file (by
  adding a frame option `allowframebreaks' -- similar to the `fragile'
  option)?

- How to get the TOC repeated when changing of section, with the new item
  highlighted?  See my manual essay ;-)

The last question has maybe few to do with Org. I mean: maybe, we can't have
that feature implemented in Org. Dunno.

Here follows an example to play with, and see what I'm talking about:

--8<---------------cut here---------------start------------->8---
#+TITLE:     Inventory
#+AUTHOR:    Seb Vauban
#+EMAIL:     no-LMehjL4SQ+Y@public.gmane.org
#+DATE:      2010-01-06
#+DESCRIPTION: 
#+KEYWORDS: 
#+LANGUAGE:  en
#+OPTIONS:   H:2 num:t toc:nil
#+OPTIONS:   TeX:t LaTeX:t skip:nil d:nil todo:t pri:t tags:not-in-toc

#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation,t]
#+BEAMER_FRAME_LEVEL: 2
#+BEAMER_HEADER_EXTRA: \usetheme{Madrid}\usecolortheme{default}
#+COLUMNS: %30ITEM %8BEAMER_env(Env) %7BEAMER_opt(Options) %6BEAMER_dovl(DefOvl) %7BEAMER_ovl(Overlay) %4BEAMER_col(Col)
#+OPTIONS: tags:nil

#+BEAMER: \frame{\frametitle{Table of Contents}\tableofcontents}


* Context

** Context
   This document is a minimal example, full of fake sentences:
   - the list of assets currently found, and
   - the things that *must*, /should/ or @could@ be developed in the coming
     months.

   Is "could" presented as an alert?

   Note that the previous slide, TOC, has a title, because I inserted it
   myself. When generated by Org, there is no frametitle.


* Current assets

** DB
*** Model
**** Schema
**** Partial X
     We extended X in order to put constraints on things (as one can
     with cardinalities).
**** What
*** Rules
**** Other
***** First
***** Second
***** Rules, with link automatically made between rule failures and contributing properties
**** Performance
***** Specialization of programs given partial data
***** Query reduction: optimize the queries so that with a minimal IO interaction the necessary data from a DB can be requested
*** Computations
**** Excel engine *IS NOT THE LAST ITEM*
*** Integrity *has a subitem* (not shown by default)
**** Seamless migrations is not visible if allowframebreaks is not set

** Workflow
*** Petri net engine
*** Workflow viewer
*** Data mining
*** Internal engine (based on new protocol)
*** Semantic language (integration of the model and of the other stuff)


* Future developments
#+BEAMER: \frame[c]{\begin{center}Future developments\end{center}}

** Model
*** Extensions (aggregation, negation)
** Workflow
*** Workflow editor


* COMMENT Setup

# This is for the sake of Emacs.
# Local Variables:
# ispell-local-dictionary: "en_US"
# End:
--8<---------------cut here---------------end--------------->8---

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: New beamer support

[Carsten Dominik]

On Jan 6, 2010, at 10:46 AM, Sébastien Vauban wrote:

> Hello all,
>
> Here a few comments, after my first attempt with the new beamer  
> support --
> excellent, needless to say...
>
> Before that, I was using Nick's export class. But, now, I'm using  
> yesterday's
> git version.
>
> The few things I'm tackling right now are:
>
> - How to get a TOC with a frame title, without having to add it  
> explicitly?

What would you like to have the LaTeX to be like?

>
> - How to get alerted text, without customizing `org-export-emphasis- 
> alist'?
>  Has this been forgotten from the commit?

I don't remember this.  Can you please remind me?

>
> - How to get "frame breaks", without modifying the resulting TeX  
> file (by
>  adding a frame option `allowframebreaks' -- similar to the `fragile'
>  option)?


Just put [allowframebreaks] into the :BEAMER_envargs: property of
the node that becomes the frame.

>
> - How to get the TOC repeated when changing of section, with the new  
> item
>  highlighted?  See my manual essay ;-)

I don't know!  Isn't this something that can be done with beamer themes?
I have no idea.

>
> The last question has maybe few to do with Org. I mean: maybe, we  
> can't have
> that feature implemented in Org. Dunno.

Beamer support is hacking Org quite a bit, installing hooks left
and right, so I think it can be done.  But I would need o know what  
exactly is needed/wanted....

- Carsten

>
> Here follows an example to play with, and see what I'm talking about:
>
> --8<---------------cut here---------------start------------->8---
> #+TITLE:     Inventory
> #+AUTHOR:    Seb Vauban
> #+EMAIL:     no@one.com
> #+DATE:      2010-01-06
> #+DESCRIPTION:
> #+KEYWORDS:
> #+LANGUAGE:  en
> #+OPTIONS:   H:2 num:t toc:nil
> #+OPTIONS:   TeX:t LaTeX:t skip:nil d:nil todo:t pri:t tags:not-in-toc
>
> #+LaTeX_CLASS: beamer
> #+LaTeX_CLASS_OPTIONS: [presentation,t]
> #+BEAMER_FRAME_LEVEL: 2
> #+BEAMER_HEADER_EXTRA: \usetheme{Madrid}\usecolortheme{default}
> #+COLUMNS: %30ITEM %8BEAMER_env(Env) %7BEAMER_opt(Options)  
> %6BEAMER_dovl(DefOvl) %7BEAMER_ovl(Overlay) %4BEAMER_col(Col)
> #+OPTIONS: tags:nil
>
> #+BEAMER: \frame{\frametitle{Table of Contents}\tableofcontents}
>
>
> * Context
>
> ** Context
>   This document is a minimal example, full of fake sentences:
>   - the list of assets currently found, and
>   - the things that *must*, /should/ or @could@ be developed in the  
> coming
>     months.
>
>   Is "could" presented as an alert?
>
>   Note that the previous slide, TOC, has a title, because I inserted  
> it
>   myself. When generated by Org, there is no frametitle.
>
>
> * Current assets
>
> ** DB
> *** Model
> **** Schema
> **** Partial X
>     We extended X in order to put constraints on things (as one can
>     with cardinalities).
> **** What
> *** Rules
> **** Other
> ***** First
> ***** Second
> ***** Rules, with link automatically made between rule failures and  
> contributing properties
> **** Performance
> ***** Specialization of programs given partial data
> ***** Query reduction: optimize the queries so that with a minimal  
> IO interaction the necessary data from a DB can be requested
> *** Computations
> **** Excel engine *IS NOT THE LAST ITEM*
> *** Integrity *has a subitem* (not shown by default)
> **** Seamless migrations is not visible if allowframebreaks is not set
>
> ** Workflow
> *** Petri net engine
> *** Workflow viewer
> *** Data mining
> *** Internal engine (based on new protocol)
> *** Semantic language (integration of the model and of the other  
> stuff)
>
>
> * Future developments
> #+BEAMER: \frame[c]{\begin{center}Future developments\end{center}}
>
> ** Model
> *** Extensions (aggregation, negation)
> ** Workflow
> *** Workflow editor
>
>
> * COMMENT Setup
>
> # This is for the sake of Emacs.
> # Local Variables:
> # ispell-local-dictionary: "en_US"
> # End:
> --8<---------------cut here---------------end--------------->8---
>
> Best regards,
>  Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> 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

- Carsten

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> Sébastien Vauban wrote:
>>
>> The few things I'm tackling right now are:
>>
>> - How to get a TOC with a frame title, without having to add it explicitly?
>
> What would you like to have the LaTeX to be like?

See the line I added manually in the example Org file:

>> #+BEAMER: \frame{\frametitle{Table of Contents}\tableofcontents}

Now, we can discuss about the right title for the TOC slide:
- Table of Contents?
- Table of contents?
- Contents?
- Index?
- Plan?

Maybe that should become a customizable variable with a nice default value...


>> - How to get alerted text, without customizing `org-export-emphasis-
>>   alist'?  Has this been forgotten from the commit?
>
> I don't remember this.  Can you please remind me?

See the discussion with Eric on
http://www.mail-archive.com/emacs-orgmode-mXXj517/zsQ@public.gmane.org/msg19862.html.

Currently (git version of 10 mins ago), I have nothing defined for `@':

--8<---------------cut here---------------start------------->8---
org-export-latex-emphasis-alist is a variable defined in `org-latex.el'.
Its value is 
(("*" "\\textbf{%s}" nil)
 ("/" "\\emph{%s}" nil)
 ("_" "\\underline{%s}" nil)
 ("+" "\\st{%s}" nil)
 ("=" "\\verb" t)
 ("~" "\\verb" t))
--8<---------------cut here---------------end--------------->8---

Shouldn't `("@" "\\alert{%s}" nil)' be added by default?


>> - How to get "frame breaks", without modifying the resulting TeX file (by
>>  adding a frame option `allowframebreaks' -- similar to the `fragile'
>>  option)?
>
> Just put [allowframebreaks] into the :BEAMER_envargs: property of
> the node that becomes the frame.

That does work. Thanks.

However, couldn't we have that on by default on all nodes? For sure, some
people won't remark some text is cut off in the output beamer presentation,
when the option is not set.

By the way, how are we supposed to add that property in the most easiest
manner?  I never really used column view, but I have troubles when using it
here.

On the node where I want to add that property, I do:
- `C-c C-x C-c' to enter column view
- `right' (arrow) to go in the second column
- `e' to edit the property
... but I'm put in a tag selection menu... What am I doing wrong?


>> - How to get the TOC repeated when changing of section, with the new item
>>  highlighted?  See my manual essay ;-)
>
> I don't know!  Isn't this something that can be done with beamer themes?
> I have no idea.

Maybe others have feedback on this. I'm not yet expert either in beamer...


>> The last question has maybe few to do with Org. I mean: maybe, we can't have
>> that feature implemented in Org. Dunno.
>
> Beamer support is hacking Org quite a bit, installing hooks left
> and right, so I think it can be done.  But I would need o know what exactly is
> needed/wanted....

Sure. Thanks -- once again -- for all excellent results achieved so far.

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: New beamer support

[Christian Lasarczyk]

Hi Sébastien and Carsten,

Carsten Dominik wrote:

>> - How to get the TOC repeated when changing of section, with the new
>> item
>>  highlighted?  See my manual essay ;-)
> 
> I don't know!  Isn't this something that can be done with beamer themes?
> I have no idea.
>

\AtBeginSection[] % Do nothing for \section*
{
  \begin{frame}<beamer>
    \frametitle{Outline}
    \tableofcontents[currentsection]
    %or \tableofcontents
  \end{frame}
}

Should do the job.

Bet regards,
   Christian

Re: New beamer support

[Eric S Fraga]

At Wed, 06 Jan 2010 10:46:45 +0100,
Sébastien Vauban wrote:
> 
> Hello all,
> 
> Here a few comments, after my first attempt with the new beamer support --
> excellent, needless to say...

Yes, excellent indeed.  

An aside: *Carsten,* I have been off ill (eye operation at start of
December) so only today have I managed to come back to play with
org-mode's beamer support.  Everything so far is working as expected,
i.e. very well indeed.

> Before that, I was using Nick's export class. But, now, I'm using yesterday's
> git version.
> 
> The few things I'm tackling right now are:
> 
> - How to get a TOC with a frame title, without having to add it explicitly?

I think you need to add it explicitly with \tableofcontents?  In beamer, I simply typically have

--8<---------------cut here---------------start------------->8---
\begin{frame}<beamer> 
  \frametitle{Table of contents}
  \tableofcontents
\end{frame}
--8<---------------cut here---------------end--------------->8---

> - How to get alerted text, without customizing `org-export-emphasis-alist'?
>   Has this been forgotten from the commit?

I think the decision was to allow users to customise this themselves
(as indicated in your subsequent followup with a link to one of our
previous messages on this topic).

> 
> - How to get "frame breaks", without modifying the resulting TeX file (by
>   adding a frame option `allowframebreaks' -- similar to the `fragile'
>   option)?
> 
> - How to get the TOC repeated when changing of section, with the new item
>   highlighted?  See my manual essay ;-)

Again, beamer supports this easily so I would suggest simply adding
some direct latex code at the start of your org file.  The latex code
I use is:

--8<---------------cut here---------------start------------->8---
\AtBeginSection[]
{
  \begin{frame}
    \frametitle{Topic}
    \tableofcontents[currentsection]
  \end{frame}
}
--8<---------------cut here---------------end--------------->8---

You could simply put this in one line with #+latex_header: as in (untested):

--8<---------------cut here---------------start------------->8---
#+latex_header: \AtBeginSection[]{  \begin{frame}    \frametitle{Topic}    \tableofcontents[currentsection]  \end{frame}}
--8<---------------cut here---------------end--------------->8---

HTH,
eric

Re: Re: New beamer support

[Carsten Dominik]

On Jan 6, 2010, at 12:13 PM, Christian Lasarczyk wrote:

> Hi Sébastien and Carsten,
>
> Carsten Dominik wrote:
>
>>> - How to get the TOC repeated when changing of section, with the new
>>> item
>>> highlighted?  See my manual essay ;-)
>>
>> I don't know!  Isn't this something that can be done with beamer  
>> themes?
>> I have no idea.
>>
>
> \AtBeginSection[] % Do nothing for \section*
> {
>  \begin{frame}<beamer>
>    \frametitle{Outline}
>    \tableofcontents[currentsection]
>    %or \tableofcontents
>  \end{frame}
> }

Hi Christian,

Do I understand correctly that this has to be set only once, and will
automatically happen at the beginning of each section?

Can this be done in the preamble, or must it be after \begin{document} ?

Thanks!

- Carsten


>
> Should do the job.
>
> Bet regards,
>   Christian
>
>
>
>
> _______________________________________________
> 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

- Carsten

Re: Re: New beamer support

[Carsten Dominik]

On Jan 6, 2010, at 11:59 AM, Sébastien Vauban wrote:

>
> Shouldn't `("@" "\\alert{%s}" nil)' be added by default?

Hmm, I am not sure, because \alert is of course not defined in normal  
LaTeX export.  And maybe it would even be better to redifine bold  
emphasis as alert for beamer export?

>
>
>>> - How to get "frame breaks", without modifying the resulting TeX  
>>> file (by
>>> adding a frame option `allowframebreaks' -- similar to the `fragile'
>>> option)?
>>
>> Just put [allowframebreaks] into the :BEAMER_envargs: property of
>> the node that becomes the frame.
>
> That does work. Thanks.
>
> However, couldn't we have that on by default on all nodes? For sure,  
> some
> people won't remark some text is cut off in the output beamer  
> presentation,
> when the option is not set.

I believe turning this on for all frames has drawbacks, like
loosing overlay capability?

However, I guess it does make sense to have a global variable to
set default options for frames, I guess.  I'll put that on my list.

>
> By the way, how are we supposed to add that property in the most  
> easiest
> manner?  I never really used column view, but I have troubles when  
> using it
> here.
>
> On the node where I want to add that property, I do:
> - `C-c C-x C-c' to enter column view
> - `right' (arrow) to go in the second column
> - `e' to edit the property
> ... but I'm put in a tag selection menu... What am I doing wrong?

That happens at the BEAMER_env property and give you a way to
select the environment with a single key, for example `e b' for block.
If you move the cursor to the field for env args, e will give you a
prompt where you can edit.

- Carsten

Re: New beamer support

[Sébastien Vauban]

Hi Eric, Christian, Carsten and all,

Eric S Fraga wrote:
> At Wed, 06 Jan 2010 10:46:45 +0100, Sébastien Vauban wrote:
>>
>> The few things I'm tackling right now are:
>>
>> - How to get a TOC with a frame title, without having to add it explicitly?
>
> I think you need to add it explicitly with \tableofcontents? In beamer, I
> simply typically have
>
> \begin{frame}<beamer>
>   \frametitle{Table of contents}
>   \tableofcontents
> \end{frame}

I guess I wasn't clear...

If I use the option `toc' for the export:

--8<---------------cut here---------------start------------->8---
#+OPTIONS:   toc:t
--8<---------------cut here---------------end--------------->8---

then I get a slide with the table of contents. Automatically. The only
"criticism" I did is that there was no title to the generated frame.

Hence, the workaround was setting the `toc' option to `nil' and adding such a
code by myself:

--8<---------------cut here---------------start------------->8---
#+BEAMER: \frame{\frametitle{Outline}\tableofcontents}
--8<---------------cut here---------------end--------------->8---

But better (IMHO) would be that such a code gets inserted automatically (with
a frame title set, for example, to `Outline') when the `toc' export option is
set to `t', and when we're in a beamer class.

Is it better expressed?


>> - How to get the TOC repeated when changing of section, with the new item
>>   highlighted? See my manual essay ;-)
>
> Again, beamer supports this easily so I would suggest simply adding some
> direct latex code at the start of your org file. The latex code I use is:
>
> \AtBeginSection[]
> {
>   \begin{frame}
>     \frametitle{Topic}
>     \tableofcontents[currentsection]
>   \end{frame}
> }
>
> You could simply put this in one line with #+latex_header: as in (untested):
>
> #+latex_header: \AtBeginSection[]{  \begin{frame}    \frametitle{Topic}    \tableofcontents[currentsection]  \end{frame}}

Better is:

--8<---------------cut here---------------start------------->8---
#+BEGIN_BEAMER
\AtBeginSection[] % Do nothing for \section*
{
  \begin{frame}<beamer>
    \frametitle{Outline}
    \tableofcontents[currentsection]
  \end{frame}
}
#+END_BEAMER
--8<---------------cut here---------------end--------------->8---

Thanks Eric and Christian for your input on this!

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Jan 6, 2010, at 12:13 PM, Christian Lasarczyk wrote:
>> Carsten Dominik wrote:
>>
>>>> - How to get the TOC repeated when changing of section, with the new
>>>> item highlighted? See my manual essay ;-)
>>>
>>> I don't know!  Isn't this something that can be done with beamer themes?
>>> I have no idea.
>>
>> \AtBeginSection[] % Do nothing for \section*
>> {
>>  \begin{frame}<beamer>
>>    \frametitle{Outline}
>>    \tableofcontents[currentsection]
>>    %or \tableofcontents
>>  \end{frame}
>> }
>
> Do I understand correctly that this has to be set only once, and will
> automatically happen at the beginning of each section?

Yes, you do.


> Can this be done in the preamble, or must it be after \begin{document} ?

It can be done in the preamble as well. Tested.

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: New beamer support

[Carsten Dominik]

Hi Sebastien,

there is now a new option org-beamer-frame-default-options, and the  
automatically generated to will be wrapped into a frame with title.

- Carsten

On Jan 6, 2010, at 2:03 PM, Sébastien Vauban wrote:

> Hi Eric, Christian, Carsten and all,
>
> Eric S Fraga wrote:
>> At Wed, 06 Jan 2010 10:46:45 +0100, Sébastien Vauban wrote:
>>>
>>> The few things I'm tackling right now are:
>>>
>>> - How to get a TOC with a frame title, without having to add it  
>>> explicitly?
>>
>> I think you need to add it explicitly with \tableofcontents? In  
>> beamer, I
>> simply typically have
>>
>> \begin{frame}<beamer>
>>  \frametitle{Table of contents}
>>  \tableofcontents
>> \end{frame}
>
> I guess I wasn't clear...
>
> If I use the option `toc' for the export:
>
> --8<---------------cut here---------------start------------->8---
> #+OPTIONS:   toc:t
> --8<---------------cut here---------------end--------------->8---
>
> then I get a slide with the table of contents. Automatically. The only
> "criticism" I did is that there was no title to the generated frame.
>
> Hence, the workaround was setting the `toc' option to `nil' and  
> adding such a
> code by myself:
>
> --8<---------------cut here---------------start------------->8---
> #+BEAMER: \frame{\frametitle{Outline}\tableofcontents}
> --8<---------------cut here---------------end--------------->8---
>
> But better (IMHO) would be that such a code gets inserted  
> automatically (with
> a frame title set, for example, to `Outline') when the `toc' export  
> option is
> set to `t', and when we're in a beamer class.
>
> Is it better expressed?
>
>
>>> - How to get the TOC repeated when changing of section, with the  
>>> new item
>>>  highlighted? See my manual essay ;-)
>>
>> Again, beamer supports this easily so I would suggest simply adding  
>> some
>> direct latex code at the start of your org file. The latex code I  
>> use is:
>>
>> \AtBeginSection[]
>> {
>>  \begin{frame}
>>    \frametitle{Topic}
>>    \tableofcontents[currentsection]
>>  \end{frame}
>> }
>>
>> You could simply put this in one line with #+latex_header: as in  
>> (untested):
>>
>> #+latex_header: \AtBeginSection[]{  \begin{frame}     
>> \frametitle{Topic}    \tableofcontents[currentsection]  \end{frame}}
>
> Better is:
>
> --8<---------------cut here---------------start------------->8---
> #+BEGIN_BEAMER
> \AtBeginSection[] % Do nothing for \section*
> {
>  \begin{frame}<beamer>
>    \frametitle{Outline}
>    \tableofcontents[currentsection]
>  \end{frame}
> }
> #+END_BEAMER
> --8<---------------cut here---------------end--------------->8---
>
> Thanks Eric and Christian for your input on this!
>
> Best regards,
>  Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> 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

- Carsten

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Jan 6, 2010, at 11:59 AM, Sébastien Vauban wrote:
>>
>> Shouldn't `("@" "\\alert{%s}" nil)' be added by default?
>
> Hmm, I am not sure, because \alert is of course not defined in normal LaTeX
> export. And maybe it would even be better to redifine bold emphasis as alert
> for beamer export?

For me, bold and alert are 2 different beasts. Some beamer styles even display
them differently (different colors, for example). Better would be not to mix
them, IMHO.


>>>> - How to get "frame breaks", without modifying the resulting TeX file (by
>>>> adding a frame option `allowframebreaks' -- similar to the `fragile'
>>>> option)?
>>>
>>> Just put [allowframebreaks] into the :BEAMER_envargs: property of
>>> the node that becomes the frame.
>>
>> That does work. Thanks.
>>
>> However, couldn't we have that on by default on all nodes? For sure, some
>> people won't remark some text is cut off in the output beamer presentation,
>> when the option is not set.
>
> I believe turning this on for all frames has drawbacks, like
> loosing overlay capability?

I'm not sure I understand the point but...


> However, I guess it does make sense to have a global variable to
> set default options for frames, I guess.  I'll put that on my list.

OK. Thanks.


>> By the way, how are we supposed to add that property in the most easiest
>> manner? I never really used column view, but I have troubles when using it
>> here.
>>
>> On the node where I want to add that property, I do:
>> - `C-c C-x C-c' to enter column view
>> - `right' (arrow) to go in the second column
>> - `e' to edit the property
>> ... but I'm put in a tag selection menu... What am I doing wrong?
>
> That happens at the BEAMER_env property and give you a way to select the
> environment with a single key, for example `e b' for block. If you move the
> cursor to the field for env args, e will give you a prompt where you can
> edit.

Whether in org-mode or in org-beamer-mode, when typing `e' on the second
column, it opens the tag selection interface in the minibuffer. But, here,
what I'm trying to add is a property, not a tag...?

Pressing TAB allows me free edition, but what's inserted at the node is a
tag...

PS- An idea: wouldn't it be good (*iff* easily feasible) to load
org-beamer-mode when opening an Org file whose LaTeX class is beamer?

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: New beamer support

[Carsten Dominik]

On Jan 6, 2010, at 2:35 PM, Sébastien Vauban wrote:

> Hi Carsten,
>
> Carsten Dominik wrote:
>> On Jan 6, 2010, at 11:59 AM, Sébastien Vauban wrote:
>>>
>>> Shouldn't `("@" "\\alert{%s}" nil)' be added by default?
>>
>> Hmm, I am not sure, because \alert is of course not defined in  
>> normal LaTeX
>> export. And maybe it would even be better to redifine bold emphasis  
>> as alert
>> for beamer export?
>
> For me, bold and alert are 2 different beasts. Some beamer styles  
> even display
> them differently (different colors, for example). Better would be  
> not to mix
> them, IMHO.
>
>
>>>>> - How to get "frame breaks", without modifying the resulting TeX  
>>>>> file (by
>>>>> adding a frame option `allowframebreaks' -- similar to the  
>>>>> `fragile'
>>>>> option)?
>>>>
>>>> Just put [allowframebreaks] into the :BEAMER_envargs: property of
>>>> the node that becomes the frame.
>>>
>>> That does work. Thanks.
>>>
>>> However, couldn't we have that on by default on all nodes? For  
>>> sure, some
>>> people won't remark some text is cut off in the output beamer  
>>> presentation,
>>> when the option is not set.
>>
>> I believe turning this on for all frames has drawbacks, like
>> loosing overlay capability?
>
> I'm not sure I understand the point but...
>
>
>> However, I guess it does make sense to have a global variable to
>> set default options for frames, I guess.  I'll put that on my list.
>
> OK. Thanks.
>
>
>>> By the way, how are we supposed to add that property in the most  
>>> easiest
>>> manner? I never really used column view, but I have troubles when  
>>> using it
>>> here.
>>>
>>> On the node where I want to add that property, I do:
>>> - `C-c C-x C-c' to enter column view
>>> - `right' (arrow) to go in the second column
>>> - `e' to edit the property
>>> ... but I'm put in a tag selection menu... What am I doing wrong?
>>
>> That happens at the BEAMER_env property and give you a way to  
>> select the
>> environment with a single key, for example `e b' for block. If you  
>> move the
>> cursor to the field for env args, e will give you a prompt where  
>> you can
>> edit.
>
> Whether in org-mode or in org-beamer-mode, when typing `e' on the  
> second
> column, it opens the tag selection interface in the minibuffer. But,  
> here,
> what I'm trying to add is a property, not a tag...?

Indeed you are changing the tag, but the property will change along
with it (check it!).  The idea is that the property is *tracked* by
a tag, to make the current value constantly visible.  I use the tag
interface just because it exists and is simple to use.

>
> Pressing TAB allows me free edition, but what's inserted at the node  
> is a
> tag...

Which will cause a change in the property as well, I believe.  I know
it is confusing - but once you've got your head around this, it will be
very useful.

>
> PS- An idea: wouldn't it be good (*iff* easily feasible) to load
> org-beamer-mode when opening an Org file whose LaTeX class is beamer?

That could be done, but you can also set the startup option.
But yes, it is one more think to remember...

- Carsten

Re: Re: New beamer support

[Carsten Dominik]

On Jan 6, 2010, at 3:23 PM, Carsten Dominik wrote:
>
>>
>> PS- An idea: wouldn't it be good (*iff* easily feasible) to load
>> org-beamer-mode when opening an Org file whose LaTeX class is beamer?
>
> That could be done, but you can also set the startup option.
> But yes, it is one more think to remember...


I remember now why I did it like this.

1. If the global LaTeX class is not beamer, you still
    want to be able to turn the mode on, because you might
    have a subtree that will be exported as beamer presentation

2. If you are not missing the `C-c C-b' key, you can just
    turn on org-beamer-mode in every org-mode by setting
    org-startup-with-beamer-mode.

- Carsten

Re: New beamer support

[Sébastien Vauban]

Carsten,

Carsten Dominik wrote:
> On Jan 6, 2010, at 3:23 PM, Carsten Dominik wrote:
>>>
>>> PS- An idea: wouldn't it be good (*iff* easily feasible) to load
>>> org-beamer-mode when opening an Org file whose LaTeX class is beamer?
>>
>> That could be done, but you can also set the startup option.
>> But yes, it is one more think to remember...
>
> I remember now why I did it like this.
>
> 1. If the global LaTeX class is not beamer, you still want to be able to
>    turn the mode on, because you might have a subtree that will be exported
>    as beamer presentation

Right.

--8<---------------cut here---------------start------------->8---
Org-Beamer minor mode (indicator Bm):
Special support for editing Org-mode files made to export to beamer.
--8<---------------cut here---------------end--------------->8---

Wouldn't it be better to rename the function to be called as `M-x
org-beamer-minor-mode'. Many minor modes are called that way, even if a quick
overview of the functions show that it does not seem to be enforced.


> 2. If you are not missing the `C-c C-b' key, you can just turn on
>    org-beamer-mode in every org-mode by setting
>    org-startup-with-beamer-mode.

Right. Not a problem.

Thanks,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: New beamer support

[Sébastien Vauban]

Carsten,

Carsten Dominik wrote:
> On Jan 6, 2010, at 2:35 PM, Sébastien Vauban wrote:
>> Carsten Dominik wrote:
>>> On Jan 6, 2010, at 11:59 AM, Sébastien Vauban wrote:
>>>>
>>>> Shouldn't `("@" "\\alert{%s}" nil)' be added by default?
>>>
>>> Hmm, I am not sure, because \alert is of course not defined in normal
>>> LaTeX export. And maybe it would even be better to redifine bold emphasis
>>> as alert for beamer export?
>>
>> For me, bold and alert are 2 different beasts. Some beamer styles even
>> display them differently (different colors, for example). Better would be
>> not to mix them, IMHO.
>>
>>
>>>>>> - How to get "frame breaks", without modifying the resulting TeX file
>>>>>>   (by adding a frame option `allowframebreaks' -- similar to the
>>>>>>   `fragile' option)?
>>>>>
>>>>> Just put [allowframebreaks] into the :BEAMER_envargs: property of the
>>>>> node that becomes the frame.
>>>>
>>>> How are we supposed to add that property in the most easiest manner? I
>>>> never really used column view, but I have troubles when using it here.
>>>
>>> That happens at the BEAMER_env property and give you a way to select the
>>> environment with a single key, for example `e b' for block. If you move
>>> the cursor to the field for env args, e will give you a prompt where you
>>> can edit.
>>
>> Whether in org-mode or in org-beamer-mode, when typing `e' on the second
>> column, it opens the tag selection interface in the minibuffer. But, here,
>> what I'm trying to add is a property, not a tag...?
>
> Indeed you are changing the tag, but the property will change along with it
> (check it!). The idea is that the property is *tracked* by a tag, to make
> the current value constantly visible. I use the tag interface just because
> it exists and is simple to use.
>
>> Pressing TAB allows me free edition, but what's inserted at the node is a
>> tag...
>
> Which will cause a change in the property as well, I believe.

I don't know if it's me, but, nope, it does not.

Look, I'm starting from such a node:

--8<---------------cut here---------------start------------->8---
* Current assets

** DB
*** Model
**** Schema
**** Partial X
     We extended X in order to put constraints on things (as one can
     with cardinalities).
**** What
*** Rules
**** Other
***** First
***** Second
***** Rules, with link automatically made between rule failures and contributing properties
**** Performance
***** Specialization of programs given partial data
***** Query reduction: optimize the queries so that with a minimal IO interaction the necessary data from a DB can be requested
*** Computations
**** Excel engine *IS NOT THE LAST ITEM*
*** Integrity *has a subitem* (not shown by default)
**** Seamless migrations is not visible if allowframebreaks is not set
--8<---------------cut here---------------end--------------->8---

Trying to add the property on the level-2 item named "DB", as you can see in
my "lossage":

--8<---------------cut here---------------start------------->8---
M-x o r g - b e <tab> a m e r <tab> m o <tab> <return>
M-x <up> <return> C-c C-x C-c <right> e b e e <tab>
[ a l l w o <backspace> <backspace> o w f r a m e s
<backspace> b r e a k s ] <return> q q <tab> <tab>
<tab> <tab> <tab> <down> <tab> <down> <tab> <up> <tab>
<tab> <up> <tab> <tab> C-h C-h l
--8<---------------cut here---------------end--------------->8---

I end up with that change:

--8<---------------cut here---------------start------------->8---
* Current assets

** DB                                            :[allowframebreaks]:B_block:
   :PROPERTIES:
   :END:
*** Model
--8<---------------cut here---------------end--------------->8---

Properties are empty.

When not typing `e b', I just end up with:

--8<---------------cut here---------------start------------->8---
** DB                                                    :[allowframebreaks]:
*** Model
--8<---------------cut here---------------end--------------->8---

No property block is created...

Maybe I still do something wrong?


> I know it is confusing - but once you've got your head around this, it will
> be very useful.

As soon as I get this working, OK, yes, not a problem, I just have to know...

Thanks,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> there is now a new option org-beamer-frame-default-options

When setting it into Emacs, great, it DOES WORK as expected!

Though, I believe this is more a setting of the document itself, instead of
one customization in my own `.emacs' file.

I would rather like my colleagues to get the same output when compiling my
document. I tried, then, the following:

--8<---------------cut here---------------start------------->8---
* COMMENT Setup

# This is for the sake of Emacs.
# Local Variables:
# ispell-local-dictionary: "en_US"
# org-beamer-frame-default-options: "[allowframebreaks]"
# End:
--8<---------------cut here---------------end--------------->8---

with no success, though.

Maybe I would have to try with a `#+BIND'. Though, wouldn't it be better to
explicitly add something like:

--8<---------------cut here---------------start------------->8---
#+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
--8<---------------cut here---------------end--------------->8---

Easy for me to (just) propose it, though...


> and the automatically generated to will be wrapped into a frame with title.

Tested. Perfect.

THANKS A LOT.

Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: New beamer support

[Carsten Dominik]

On Jan 6, 2010, at 4:35 PM, Sébastien Vauban wrote:

> Carsten,
>
> Carsten Dominik wrote:
>> On Jan 6, 2010, at 3:23 PM, Carsten Dominik wrote:
>>>>
>>>> PS- An idea: wouldn't it be good (*iff* easily feasible) to load
>>>> org-beamer-mode when opening an Org file whose LaTeX class is  
>>>> beamer?
>>>
>>> That could be done, but you can also set the startup option.
>>> But yes, it is one more think to remember...
>>
>> I remember now why I did it like this.
>>
>> 1. If the global LaTeX class is not beamer, you still want to be  
>> able to
>>  turn the mode on, because you might have a subtree that will be  
>> exported
>>  as beamer presentation
>
> Right.
>
> --8<---------------cut here---------------start------------->8---
> Org-Beamer minor mode (indicator Bm):
> Special support for editing Org-mode files made to export to beamer.
> --8<---------------cut here---------------end--------------->8---
>
> Wouldn't it be better to rename the function to be called as `M-x
> org-beamer-minor-mode'. Many minor modes are called that way, even  
> if a quick
> overview of the functions show that it does not seem to be enforced.

No, I think putting minor into the name is a mistake.  The only place
where this makes sense is something like outline-minor-mode, i.e. where
a major mode of the same name exists.

- Carsten

>
>
>> 2. If you are not missing the `C-c C-b' key, you can just turn on
>>  org-beamer-mode in every org-mode by setting
>>  org-startup-with-beamer-mode.
>
> Right. Not a problem.
>
> Thanks,
> Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> 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

- Carsten

Re: Re: New beamer support

[Carsten Dominik]

On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:

> Hi Carsten,
>
> Carsten Dominik wrote:
>> there is now a new option org-beamer-frame-default-options
>
> When setting it into Emacs, great, it DOES WORK as expected!
>
> Though, I believe this is more a setting of the document itself,  
> instead of
> one customization in my own `.emacs' file.
>
> I would rather like my colleagues to get the same output when  
> compiling my
> document. I tried, then, the following:
>
> --8<---------------cut here---------------start------------->8---
> * COMMENT Setup
>
> # This is for the sake of Emacs.
> # Local Variables:
> # ispell-local-dictionary: "en_US"
> # org-beamer-frame-default-options: "[allowframebreaks]"
> # End:
> --8<---------------cut here---------------end--------------->8---
>
> with no success, though.
>
> Maybe I would have to try with a `#+BIND'.


#+BIND will do the trick, it was made just for this.

> Though, wouldn't it be better to
> explicitly add something like:
>
> --8<---------------cut here---------------start------------->8---
> #+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
> --8<---------------cut here---------------end--------------->8---

Yes, that would make sense if it is a frequently used feature.
I like to hesitate with introducing these special customizations
until I am convinced that this is used reasonably often.  Otherwise
I would have to have 1000 of the special lines, approximately.

Question to all:  How likely is the use of a default option you'd
want to have on *every* frame?

- Carsten

Re: Re: New beamer support

[Carsten Dominik]

On Jan 6, 2010, at 4:47 PM, Sébastien Vauban wrote:
> Trying to add the property on the level-2 item named "DB", as you  
> can see in
> my "lossage":
>
> --8<---------------cut here---------------start------------->8---
> M-x o r g - b e <tab> a m e r <tab> m o <tab> <return>
> M-x <up> <return> C-c C-x C-c <right> e b e e <tab>
> [ a l l w o <backspace> <backspace> o w f r a m e s
> <backspace> b r e a k s ] <return> q q <tab> <tab>
> <tab> <tab> <tab> <down> <tab> <down> <tab> <up> <tab>
> <tab> <up> <tab> <tab> C-h C-h l
> --8<---------------cut here---------------end--------------->8---
>
> I end up with that change:
>
> --8<---------------cut here---------------start------------->8---
> * Current assets
>
> ** DB                                            : 
> [allowframebreaks]:B_block:
>  :PROPERTIES:
>  :END:
> *** Model
> --8<---------------cut here---------------end--------------->8---
>
> Properties are empty.
>
> When not typing `e b', I just end up with:
>
> --8<---------------cut here---------------start------------->8---
> ** DB                                                    : 
> [allowframebreaks]:
> *** Model
> --8<---------------cut here---------------end--------------->8---
>
> No property block is created...


I believe I have said several times that the second column is *not* the
one for the options.  The third is.

- Carsten

>
> Maybe I still do something wrong?
>
>
>> I know it is confusing - but once you've got your head around this,  
>> it will
>> be very useful.
>
> As soon as I get this working, OK, yes, not a problem, I just have  
> to know...
>
> Thanks,
> Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> 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

- Carsten

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
>> Carsten Dominik wrote:
>>> there is now a new option org-beamer-frame-default-options
>>
>> When setting it into Emacs, great, it DOES WORK as expected!
>>
>> Though, I believe this is more a setting of the document itself, instead of
>> one customization in my own `.emacs' file.
>>
>> I would rather like my colleagues to get the same output when compiling my
>> document. I tried, then, the following:
>>
>> --8<---------------cut here---------------start------------->8---
>> * COMMENT Setup
>>
>> # This is for the sake of Emacs.
>> # Local Variables:
>> # ispell-local-dictionary: "en_US"
>> # org-beamer-frame-default-options: "[allowframebreaks]"
>> # End:
>> --8<---------------cut here---------------end--------------->8---
>>
>> with no success, though.
>>
>> Maybe I would have to try with a `#+BIND'.
>
> #+BIND will do the trick, it was made just for this.

#+BIND: org-beamer-frame-default-options "[allowframebreaks]"

does work.


>> Though, wouldn't it be better to
>> explicitly add something like:
>>
>> --8<---------------cut here---------------start------------->8---
>> #+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
>> --8<---------------cut here---------------end--------------->8---
>
> Yes, that would make sense if it is a frequently used feature.
> I like to hesitate with introducing these special customizations
> until I am convinced that this is used reasonably often.  Otherwise
> I would have to have 1000 of the special lines, approximately.
>
> Question to all:  How likely is the use of a default option you'd
> want to have on *every* frame?

The problem is similar to the `fragile' option. Either we can detect the
"overflow" (and the automatically add the option only when needed), or we must
add it everywhere in order to ensure we won't have text cut.

It's a bit different from when we directly edit beamer files. We compile often
and we see the problem appearing.

Here, with Org, we would just work in Org only, and publish once at the end. A
bit more easy to be aware that some text may have pass away.

As #+BIND works, I can imagine living quite honestly the way it currently is,
but I let the others decide upon this.

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
>> Carsten Dominik wrote:
>>> there is now a new option org-beamer-frame-default-options
>>
>> When setting it into Emacs, great, it DOES WORK as expected!
>>
>> Though, I believe this is more a setting of the document itself, instead of
>> one customization in my own `.emacs' file.
>>
>> Maybe I would have to try with a `#+BIND'.
>
> #+BIND will do the trick, it was made just for this.

As said previously, yes, it does work for the exporting to beamer TeX file.

Though, I experience a bigger problem... When reopening my example file, I now
have to answer "yes or no" to apply the BIND variable (that's OK), but (after
answering yes -- no tested with no, as that's not what I need) I loose all the
colors in my Org buffer: the Org file becomes black only, in fixed font! All
the font locking is away, making the Org file more or less useless (as if I
would edit it with Notepad).

Any idea??

For info, the "black and white" phenomenon is propagated to the Summary buffer
of Gnus as well. No idea...

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: New beamer support

[Carsten Dominik]

On Jan 7, 2010, at 9:54 AM, Sébastien Vauban wrote:

> Hi Carsten,
>
> Carsten Dominik wrote:
>> On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
>>> Carsten Dominik wrote:
>>>> there is now a new option org-beamer-frame-default-options
>>>
>>> When setting it into Emacs, great, it DOES WORK as expected!
>>>
>>> Though, I believe this is more a setting of the document itself,  
>>> instead of
>>> one customization in my own `.emacs' file.
>>>
>>> Maybe I would have to try with a `#+BIND'.
>>
>> #+BIND will do the trick, it was made just for this.
>
> As said previously, yes, it does work for the exporting to beamer  
> TeX file.
>
> Though, I experience a bigger problem... When reopening my example  
> file, I now
> have to answer "yes or no" to apply the BIND variable (that's OK),  
> but (after
> answering yes -- no tested with no, as that's not what I need) I  
> loose all the
> colors in my Org buffer: the Org file becomes black only, in fixed  
> font! All
> the font locking is away, making the Org file more or less useless  
> (as if I
> would edit it with Notepad).
>
> Any idea??

Hi Sebastian,

Can you please turn on debug-on-quit, and then quit at the prompt and  
show me the backtrace?  Because I do not get this by simply visiting a  
file.

- Carsten

>
> For info, the "black and white" phenomenon is propagated to the  
> Summary buffer
> of Gnus as well. No idea...
>
> Best regards,
>  Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> 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

- Carsten

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Jan 6, 2010, at 4:47 PM, Sébastien Vauban wrote:
>>
>> Properties are empty.
>>
>> When not typing `e b', I just end up with:
>>
>> --8<---------------cut here---------------start------------->8---
>> ** DB                                                    :
>> [allowframebreaks]:
>> *** Model
>> --8<---------------cut here---------------end--------------->8---
>>
>> No property block is created...
>
> I believe I have said several times that the second column is *not* the
> one for the options.  The third is.

Okaaayyy...

I wouldn't say you "said" it several times, but when re-reading this, yes, you
mentioned it, but my eyes passed over it...

>>>> By the way, how are we supposed to add that property in the most easiest
>>>> manner? I never really used column view, but I have troubles when using
>>>> it here.
>>>>
>>>> On the node where I want to add that property, I do:
>>>> - `C-c C-x C-c' to enter column view
>>>> - `right' (arrow) to go in the second column
>>>> - `e' to edit the property
>>>> ... but I'm put in a tag selection menu... What am I doing wrong?
>>>
>>> That happens at the BEAMER_env property and give you a way to select the
>>> environment with a single key, for example `e b' for block. If you move
>>> the cursor to the field for env args, e will give you a prompt where you
>>> can edit.

Though, I really am sorry to waste your time with silly problems, but I still
have troubles editing this through the interface.

--8<---------------cut here---------------start------------->8---
ITEM                            | Env   | Options | DefOvl | Overlay | Col  |
--8<---------------cut here---------------end--------------->8---

Editing in the second column ("Env") does only create a tag, as mentioned in
my previous posts.

The third one ("Options") allows inserting a string without passing through
the tag interface. There, I insert the string `[allowframebreaks]'.

Though, the property created is `BEAMER_opt', not `BEAMER_envargs'??

--8<---------------cut here---------------start------------->8---
** Model                                                 :[allowframebreaks]:
*** Extensions (aggregation, negation)
** DB  
   :PROPERTIES:
   :BEAMER_opt: [allowframebreaks]
   :END:  
*** Subitem
--8<---------------cut here---------------end--------------->8---

So, this does not add the option `allowframebreaks' to the frames...

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Jan 7, 2010, at 9:54 AM, Sébastien Vauban wrote:
>> Carsten Dominik wrote:
>>>
>>> #+BIND will do the trick, it was made just for this.
>>
>> As said previously, yes, it does work for the exporting to beamer TeX file.
>>
>> Though, I experience a bigger problem... When reopening my example file, I
>> now have to answer "yes or no" to apply the BIND variable (that's OK), but
>> (after answering yes -- no tested with no, as that's not what I need) I
>> loose all the colors in my Org buffer: the Org file becomes black only, in
>> fixed font! All the font locking is away, making the Org file more or less
>> useless (as if I would edit it with Notepad).
>>
>> Any idea??
>
> Can you please turn on debug-on-quit, and then quit at the prompt and show
> me the backtrace? Because I do not get this by simply visiting a file.

Here it is.

--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (quit)
  yes-or-no-p("Allow BIND values in this buffer? ")
  org-export-confirm-letbind()
  org-infile-export-plist()
  org-default-export-plist()
  org-compute-latex-and-specials-regexp()
  org-set-regexps-and-options()
  org-mode()
  set-auto-mode-0(org-mode nil)
  set-auto-mode()
  normal-mode(t)
  after-find-file(nil t)
  find-file-noselect-1(#<buffer ecm.txt> "~/Projects/MC/ecm.txt" nil nil "~/Projects/MC/ecm.txt" (4066232 2052))
  find-file-noselect("~/Projects/MC/ecm.txt" nil nil nil)
  find-file("~/Projects/MC/ecm.txt")
  recentf-open-files-action((link :tag "[1] ~/Projects/MC/ecm.txt" :button-prefix "" :button-suffix "" :button-face default :format "%[%t\n%]" :help-echo "Open ~/Projects/MC/ecm.txt" :action recentf-open-files-action :args nil :value "~/Projects/MC/ecm.txt" :parent (group :args (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :indent 2 :format "\n%v\n" :children (#0 ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :from #<marker (moves after insertion) in no buffer> :to #<marker in no buffer>) :indent 2 :button-overlay #<overlay in no buffer> :from #<marker (moves after insertion) in no buffer> :to #<marker in no buffer>) nil)
  widget-apply((link :tag "[1] ~/Projects/MC/ecm.txt" :button-prefix "" :button-suffix "" :button-face default :format "%[%t\n%]" :help-echo "Open ~/Projects/MC/ecm.txt" :action recentf-open-files-action :args nil :value "~/Projects/MC/ecm.txt" :parent (group :args (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :indent 2 :format "\n%v\n" :children (#0 ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :from #<marker (moves after insertion) in no buffer> :to #<marker in no buffer>) :indent 2 :button-overlay #<overlay in no buffer> :from #<marker (moves after insertion) in no buffer> :to #<marker in no buffer>) :action nil)
  widget-apply-action((link :tag "[1] ~/Projects/MC/ecm.txt" :button-prefix "" :button-suffix "" :button-face default :format "%[%t\n%]" :help-echo "Open ~/Projects/MC/ecm.txt" :action recentf-open-files-action :args nil :value "~/Projects/MC/ecm.txt" :parent (group :args (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :indent 2 :format "\n%v\n" :children (#0 ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :from #<marker (moves after insertion) in no buffer> :to #<marker in no buffer>) :indent 2 :button-overlay #<overlay in no buffer> :from #<marker (moves after insertion) in no buffer> :to #<marker in no buffer>) nil)
  widget-button-press(109)
  call-interactively(widget-button-press nil nil)
--8<---------------cut here---------------end--------------->8---

Does this help you/me?

Best regards,
  Seb

PS- The extension is `.txt', but the mode associated to text file is well Org.

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: New beamer support

[Carsten Dominik]

On Jan 7, 2010, at 10:47 AM, Sébastien Vauban wrote:

> Hi Carsten,
>
> Carsten Dominik wrote:
>> On Jan 7, 2010, at 9:54 AM, Sébastien Vauban wrote:
>>> Carsten Dominik wrote:
>>>>
>>>> #+BIND will do the trick, it was made just for this.
>>>
>>> As said previously, yes, it does work for the exporting to beamer  
>>> TeX file.
>>>
>>> Though, I experience a bigger problem... When reopening my example  
>>> file, I
>>> now have to answer "yes or no" to apply the BIND variable (that's  
>>> OK), but
>>> (after answering yes -- no tested with no, as that's not what I  
>>> need) I
>>> loose all the colors in my Org buffer: the Org file becomes black  
>>> only, in
>>> fixed font! All the font locking is away, making the Org file more  
>>> or less
>>> useless (as if I would edit it with Notepad).
>>>
>>> Any idea??
>>
>> Can you please turn on debug-on-quit, and then quit at the prompt  
>> and show
>> me the backtrace? Because I do not get this by simply visiting a  
>> file.
>
> Here it is.
>
> --8<---------------cut here---------------start------------->8---
> Debugger entered--Lisp error: (quit)
>  yes-or-no-p("Allow BIND values in this buffer? ")
>  org-export-confirm-letbind()
>  org-infile-export-plist()
>  org-default-export-plist()
>  org-compute-latex-and-specials-regexp()

Ah, OK, thanks.  This is fixed now.

- Carsten

>  org-set-regexps-and-options()
>  org-mode()
>  set-auto-mode-0(org-mode nil)
>  set-auto-mode()
>  normal-mode(t)
>  after-find-file(nil t)
>  find-file-noselect-1(#<buffer ecm.txt> "~/Projects/MC/ecm.txt" nil  
> nil "~/Projects/MC/ecm.txt" (4066232 2052))
>  find-file-noselect("~/Projects/MC/ecm.txt" nil nil nil)
>  find-file("~/Projects/MC/ecm.txt")
>  recentf-open-files-action((link :tag "[1] ~/Projects/MC/ 
> ecm.txt" :button-prefix "" :button-suffix "" :button-face  
> default :format "%[%t\n%]" :help-echo "Open ~/Projects/MC/ 
> ecm.txt" :action recentf-open-files-action :args nil :value "~/ 
> Projects/MC/ecm.txt" :parent (group :args  
> (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :indent 
>  2 :format "\n%v\n" :children  
> (#0 
>  ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :from 
>  #<marker (moves after insertion) in no buffer> :to #<marker in no  
> buffer>) :indent 2 :button-overlay #<overlay in no buffer> :from  
> #<marker (moves after insertion) in no buffer> :to #<marker in no  
> buffer>) nil)
>  widget-apply((link :tag "[1] ~/Projects/MC/ecm.txt" :button-prefix  
> "" :button-suffix "" :button-face default :format "%[%t\n%]" :help- 
> echo "Open ~/Projects/MC/ecm.txt" :action recentf-open-files- 
> action :args nil :value "~/Projects/MC/ecm.txt" :parent (group :args  
> (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :indent 
>  2 :format "\n%v\n" :children  
> (#0 
>  ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :from 
>  #<marker (moves after insertion) in no buffer> :to #<marker in no  
> buffer>) :indent 2 :button-overlay #<overlay in no buffer> :from  
> #<marker (moves after insertion) in no buffer> :to #<marker in no  
> buffer>) :action nil)
>  widget-apply-action((link :tag "[1] ~/Projects/MC/ecm.txt" :button- 
> prefix "" :button-suffix "" :button-face default :format "%[%t\n 
> %]" :help-echo "Open ~/Projects/MC/ecm.txt" :action recentf-open- 
> files-action :args nil :value "~/Projects/MC/ecm.txt" :parent  
> (group :args  
> (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :indent 
>  2 :format "\n%v\n" :children  
> (#0 
>  ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :from 
>  #<marker (moves after insertion) in no buffer> :to #<marker in no  
> buffer>) :indent 2 :button-overlay #<overlay in no buffer> :from  
> #<marker (moves after insertion) in no buffer> :to #<marker in no  
> buffer>) nil)
>  widget-button-press(109)
>  call-interactively(widget-button-press nil nil)
> --8<---------------cut here---------------end--------------->8---
>
> Does this help you/me?
>
> Best regards,
>  Seb
>
> PS- The extension is `.txt', but the mode associated to text file is  
> well Org.
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> 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

- Carsten

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Jan 7, 2010, at 10:47 AM, Sébastien Vauban wrote:
>> Carsten Dominik wrote:
>>> On Jan 7, 2010, at 9:54 AM, Sébastien Vauban wrote:
>>>> Carsten Dominik wrote:
>>>>>
>>>>> #+BIND will do the trick, it was made just for this.
>>>>
>>>> Though, I experience a bigger problem... When reopening my example file,
>>>> I now have to answer "yes or no" to apply the BIND variable (that's OK),
>>>> but (after answering yes -- no tested with no, as that's not what I need)
>>>> I loose all the colors in my Org buffer: the Org file becomes black only,
>>>> in fixed font! All the font locking is away, making the Org file more or
>>>> less useless (as if I would edit it with Notepad).
>>>>
>>>> Any idea??
>>>
>>> Can you please turn on debug-on-quit, and then quit at the prompt and show
>>> me the backtrace? Because I do not get this by simply visiting a file.
>>
>> Here it is.
>>
>> --8<---------------cut here---------------start------------->8---
>> Debugger entered--Lisp error: (quit)
>>  yes-or-no-p("Allow BIND values in this buffer? ")
>>  org-export-confirm-letbind()
>>  org-infile-export-plist()
>>  org-default-export-plist()
>>  org-compute-latex-and-specials-regexp()
>
> Ah, OK, thanks.  This is fixed now.

Just did `git pull':

--8<---------------cut here---------------start------------->8---
remote: Counting objects: 23, done.
remote: Compressing objects: 100% (14/14), done.
remote: Total 14 (delta 10), reused 0 (delta 0)
Unpacking objects: 100% (14/14), done.
From git://repo.or.cz/org-mode
   c7f25c6..1596144  master     -> origin/master
Updating c7f25c6..1596144
Fast forward
 contrib/babel/lisp/langs/org-babel-clojure.el |   95 +++++++++++++++++++-----
 lisp/ChangeLog                                |    5 ++
 lisp/org.el                                   |    1 +
 3 files changed, 81 insertions(+), 20 deletions(-)
--8<---------------cut here---------------end--------------->8---

Restarted Emacs.
Re-opened my file.
Answered `yes'.
But still got the same "black-and-white" buffer...

Same impact in Gnus.

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: New beamer support

[Carsten Dominik]

Hi Sebastian, my mistake, fixed now.

- Carsten

On Jan 7, 2010, at 11:21 AM, Sébastien Vauban wrote:

> Hi Carsten,
>
> Carsten Dominik wrote:
>> On Jan 7, 2010, at 10:47 AM, Sébastien Vauban wrote:
>>> Carsten Dominik wrote:
>>>> On Jan 7, 2010, at 9:54 AM, Sébastien Vauban wrote:
>>>>> Carsten Dominik wrote:
>>>>>>
>>>>>> #+BIND will do the trick, it was made just for this.
>>>>>
>>>>> Though, I experience a bigger problem... When reopening my  
>>>>> example file,
>>>>> I now have to answer "yes or no" to apply the BIND variable  
>>>>> (that's OK),
>>>>> but (after answering yes -- no tested with no, as that's not  
>>>>> what I need)
>>>>> I loose all the colors in my Org buffer: the Org file becomes  
>>>>> black only,
>>>>> in fixed font! All the font locking is away, making the Org file  
>>>>> more or
>>>>> less useless (as if I would edit it with Notepad).
>>>>>
>>>>> Any idea??
>>>>
>>>> Can you please turn on debug-on-quit, and then quit at the prompt  
>>>> and show
>>>> me the backtrace? Because I do not get this by simply visiting a  
>>>> file.
>>>
>>> Here it is.
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> Debugger entered--Lisp error: (quit)
>>> yes-or-no-p("Allow BIND values in this buffer? ")
>>> org-export-confirm-letbind()
>>> org-infile-export-plist()
>>> org-default-export-plist()
>>> org-compute-latex-and-specials-regexp()
>>
>> Ah, OK, thanks.  This is fixed now.
>
> Just did `git pull':
>
> --8<---------------cut here---------------start------------->8---
> remote: Counting objects: 23, done.
> remote: Compressing objects: 100% (14/14), done.
> remote: Total 14 (delta 10), reused 0 (delta 0)
> Unpacking objects: 100% (14/14), done.
> From git://repo.or.cz/org-mode
>   c7f25c6..1596144  master     -> origin/master
> Updating c7f25c6..1596144
> Fast forward
> contrib/babel/lisp/langs/org-babel-clojure.el |   95 ++++++++++++++++ 
> +++-----
> lisp/ChangeLog                                |    5 ++
> lisp/org.el                                   |    1 +
> 3 files changed, 81 insertions(+), 20 deletions(-)
> --8<---------------cut here---------------end--------------->8---
>
> Restarted Emacs.
> Re-opened my file.
> Answered `yes'.
> But still got the same "black-and-white" buffer...
>
> Same impact in Gnus.
>
> Best regards,
>  Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> 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

- Carsten

Re: Re: New beamer support

[Carsten Dominik]

On Jan 7, 2010, at 10:38 AM, Sébastien Vauban wrote:

> Hi Carsten,
>
> Carsten Dominik wrote:
>> On Jan 6, 2010, at 4:47 PM, Sébastien Vauban wrote:
>>>
>>> Properties are empty.
>>>
>>> When not typing `e b', I just end up with:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> ** DB                                                    :
>>> [allowframebreaks]:
>>> *** Model
>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> No property block is created...
>>
>> I believe I have said several times that the second column is *not*  
>> the
>> one for the options.  The third is.
>
> Okaaayyy...
>
> I wouldn't say you "said" it several times, but when re-reading  
> this, yes, you
> mentioned it, but my eyes passed over it...
>
>>>>> By the way, how are we supposed to add that property in the most  
>>>>> easiest
>>>>> manner? I never really used column view, but I have troubles  
>>>>> when using
>>>>> it here.
>>>>>
>>>>> On the node where I want to add that property, I do:
>>>>> - `C-c C-x C-c' to enter column view
>>>>> - `right' (arrow) to go in the second column
>>>>> - `e' to edit the property
>>>>> ... but I'm put in a tag selection menu... What am I doing wrong?
>>>>
>>>> That happens at the BEAMER_env property and give you a way to  
>>>> select the
>>>> environment with a single key, for example `e b' for block. If  
>>>> you move
>>>> the cursor to the field for env args, e will give you a prompt  
>>>> where you
>>>> can edit.
>
> Though, I really am sorry to waste your time with silly problems,  
> but I still
> have troubles editing this through the interface.
>
> --8<---------------cut here---------------start------------->8---
> ITEM                            | Env   | Options | DefOvl | Overlay  
> | Col  |
> --8<---------------cut here---------------end--------------->8---

OK, this is helpful.  You are not using the most recent version of
the columns template for beamer support.  For example, the BEAMER_opt  
property is not used anymore.

Can you use a new file and insert a fresh template, and take it from  
there?

- Carsten

>
> Editing in the second column ("Env") does only create a tag, as  
> mentioned in
> my previous posts.
>
> The third one ("Options") allows inserting a string without passing  
> through
> the tag interface. There, I insert the string `[allowframebreaks]'.
>
> Though, the property created is `BEAMER_opt', not `BEAMER_envargs'??
>
> --8<---------------cut here---------------start------------->8---
> ** Model                                                 : 
> [allowframebreaks]:
> *** Extensions (aggregation, negation)
> ** DB
>   :PROPERTIES:
>   :BEAMER_opt: [allowframebreaks]
>   :END:
> *** Subitem
> --8<---------------cut here---------------end--------------->8---
>
> So, this does not add the option `allowframebreaks' to the frames...
>
> Best regards,
>  Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> 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

- Carsten

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Jan 7, 2010, at 10:38 AM, Sébastien Vauban wrote:
>> Carsten Dominik wrote:
>>> On Jan 6, 2010, at 4:47 PM, Sébastien Vauban wrote:
>>>>
>>>> Properties are empty.
>>>>
>>>> When not typing `e b', I just end up with:
>>>>
>>>> --8<---------------cut here---------------start------------->8---
>>>> ** DB                                                    :
>>>> [allowframebreaks]:
>>>> *** Model
>>>> --8<---------------cut here---------------end--------------->8---
>>>>
>>>> No property block is created...
>>>
>>> I believe I have said several times that the second column is *not* the
>>> one for the options.  The third is.
>>
>> I still have troubles editing this through the interface.
>>
>> --8<---------------cut here---------------start------------->8---
>> ITEM                 | Env   | Options | DefOvl | Overlay | Col |
>> --8<---------------cut here---------------end--------------->8---
>
> OK, this is helpful. You are not using the most recent version of the
> columns template for beamer support. For example, the BEAMER_opt property is
> not used anymore.

Must have taken it from a previous post here, or from your initial example.
Sorry.


> Can you use a new file and insert a fresh template, and take it from there?

Just updated the COLUMNS line in my file:

--8<---------------cut here---------------start------------->8---
#+COLUMNS: %40ITEM %10BEAMER_env(Env) %10BEAMER_envargs(Env Args) %4BEAMER_col(Col) %8BEAMER_extra(Extra)
--8<---------------cut here---------------end--------------->8---

And that does work.

Thanks for spotting this...

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: New beamer support

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
>>
>> I still got the same "black-and-white" buffer...
>
> my mistake

So... You're just a plain human?  ;-))  I'm falling from high.


> fixed now.

Yep. It does work!

Comment about this `allowframebreaks' story: I've just seen, using the
defaults (and Madrid), that the consequence of putting `allowframebreaks' on
every frame is that it adds a roman number after the title, like:

  * First slide I
  * First slide II
  * Second slide I
  * Third slide I

So, even for slides not spread across multiple pages, it adds an annoying
number (for the second and third slides).

The only solution would be that Org or the user just adds the property where
needed. For Org, it seems impossible. So, up to the user in the default
configuration.

The beamer solution is to play with:

--8<---------------cut here---------------start------------->8---
\setbeamertemplate{frametitle continuation}[from second]
%                                           ^^^^^^^^^^^

\renewcommand\insertcontinuationtext{...}
--8<---------------cut here---------------end--------------->8---

Thanks a lot.

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[beamer] Order in preamble

[Sébastien Vauban]

Hi Carsten,

Another suggestion. I think the order of macros would be better changed in the
beamer preamble.

Instead of:

--8<---------------cut here---------------start------------->8---
\usepackage{listings}


\title{Inventory}
\author{Seb Vauban}
\date{2010-01-07}

\usetheme{mc}\usecolortheme{default}
\begin{document}
--8<---------------cut here---------------end--------------->8---

I think the following is better suited:

--8<---------------cut here---------------start------------->8---
\usepackage{listings}

\usetheme{mc}\usecolortheme{default}

\title{Inventory}
\author{Seb Vauban}
\date{2010-01-07}

\begin{document}
--8<---------------cut here---------------end--------------->8---

The reason is that the natural order of packages loaded is:

- the beamer class
- the beamer theme overrides
- the document overrides

That allows one to write a private theme, and set things up (like a default
author or title) that won't take precedence over the *document settings*.

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [beamer] Order in preamble

[Carsten Dominik]

On Jan 7, 2010, at 12:30 PM, Sébastien Vauban wrote:

> Hi Carsten,
>
> Another suggestion. I think the order of macros would be better  
> changed in the
> beamer preamble.

OK, I have implemented that.  Please test it.

Thanks.

- Carsten

>
> Instead of:
>
> --8<---------------cut here---------------start------------->8---
> \usepackage{listings}
>
>
> \title{Inventory}
> \author{Seb Vauban}
> \date{2010-01-07}
>
> \usetheme{mc}\usecolortheme{default}
> \begin{document}
> --8<---------------cut here---------------end--------------->8---
>
> I think the following is better suited:
>
> --8<---------------cut here---------------start------------->8---
> \usepackage{listings}
>
> \usetheme{mc}\usecolortheme{default}
>
> \title{Inventory}
> \author{Seb Vauban}
> \date{2010-01-07}
>
> \begin{document}
> --8<---------------cut here---------------end--------------->8---
>
> The reason is that the natural order of packages loaded is:
>
> - the beamer class
> - the beamer theme overrides
> - the document overrides
>
> That allows one to write a private theme, and set things up (like a  
> default
> author or title) that won't take precedence over the *document  
> settings*.
>
> Best regards,
>  Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> 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

- Carsten

Re: Re: New beamer support

[Darlan Cavalcante Moreira]

I don't think org-mode should try to detect when to use any of the frame options
in beamer. This could get into the way more then helping, specially the
allowframebreaks option.

In fact, the beamer manual tells you not to use the allowframebreaks option
except for long bibliographies (well, it also tells you not to use long
bibliographies) and I agree with this. In a presentation you have to choose
carefully what you will put in each slide and always leaving this to beamer with
the allowframebreaks is not a good approach.

In addition, I agree that when working in a presentation with org-mode you
compile much less, but you should still compile sometimes to see if the slides
are well designed. I don't know if Carsten has plans to implement this, but a
"fast preview" that exports and compiles only the current slide could be useful
here.

At last, I have a small feature request that would help organizing the
information among the slides. Right now you can use Alt+up/down arrow to move a
list item in a heading, but org does not allow passing beyond a heading
limit. This makes sense in a normal org file and is very useful, but when
writing a presentation with org this restriction can get into the way. This is
not a big deal, but maybe others are also interested in this.

- Darlan Cavalcante Moreira

At Thu, 07 Jan 2010 09:41:29 +0100,
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> 
> Hi Carsten,
> 
> Carsten Dominik wrote:
> > On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
> >> Carsten Dominik wrote:
> >>> there is now a new option org-beamer-frame-default-options
> >>
> >> When setting it into Emacs, great, it DOES WORK as expected!
> >>
> >> Though, I believe this is more a setting of the document itself, instead of
> >> one customization in my own `.emacs' file.
> >>
> >> I would rather like my colleagues to get the same output when compiling my
> >> document. I tried, then, the following:
> >>
> >> --8<---------------cut here---------------start------------->8---
> >> * COMMENT Setup
> >>
> >> # This is for the sake of Emacs.
> >> # Local Variables:
> >> # ispell-local-dictionary: "en_US"
> >> # org-beamer-frame-default-options: "[allowframebreaks]"
> >> # End:
> >> --8<---------------cut here---------------end--------------->8---
> >>
> >> with no success, though.
> >>
> >> Maybe I would have to try with a `#+BIND'.
> >
> > #+BIND will do the trick, it was made just for this.
> 
> #+BIND: org-beamer-frame-default-options "[allowframebreaks]"
> 
> does work.
> 
> 
> >> Though, wouldn't it be better to
> >> explicitly add something like:
> >>
> >> --8<---------------cut here---------------start------------->8---
> >> #+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
> >> --8<---------------cut here---------------end--------------->8---
> >
> > Yes, that would make sense if it is a frequently used feature.
> > I like to hesitate with introducing these special customizations
> > until I am convinced that this is used reasonably often.  Otherwise
> > I would have to have 1000 of the special lines, approximately.
> >
> > Question to all:  How likely is the use of a default option you'd
> > want to have on *every* frame?
> 
> The problem is similar to the `fragile' option. Either we can detect the
> "overflow" (and the automatically add the option only when needed), or we must
> add it everywhere in order to ensure we won't have text cut.
> 
> It's a bit different from when we directly edit beamer files. We compile often
> and we see the problem appearing.
> 
> Here, with Org, we would just work in Org only, and publish once at the end. A
> bit more easy to be aware that some text may have pass away.
> 
> As #+BIND works, I can imagine living quite honestly the way it currently is,
> but I let the others decide upon this.
> 
> Best regards,
>   Seb
> 
> -- 
> Sébastien Vauban
> 
> 
> 
> _______________________________________________
> 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

Re: Re: New beamer support

[Carsten Dominik]

On Jan 7, 2010, at 3:39 PM, Darlan Cavalcante Moreira wrote:

>
> I don't think org-mode should try to detect when to use any of the  
> frame options
> in beamer. This could get into the way more then helping, specially  
> the
> allowframebreaks option.

Do you also think I should not try to add the fragile option  
automatically?

- Carsten

>
> In fact, the beamer manual tells you not to use the allowframebreaks  
> option
> except for long bibliographies (well, it also tells you not to use  
> long
> bibliographies) and I agree with this. In a presentation you have to  
> choose
> carefully what you will put in each slide and always leaving this to  
> beamer with
> the allowframebreaks is not a good approach.
>
> In addition, I agree that when working in a presentation with org- 
> mode you
> compile much less, but you should still compile sometimes to see if  
> the slides
> are well designed. I don't know if Carsten has plans to implement  
> this, but a
> "fast preview" that exports and compiles only the current slide  
> could be useful
> here.
>
> At last, I have a small feature request that would help organizing the
> information among the slides. Right now you can use Alt+up/down  
> arrow to move a
> list item in a heading, but org does not allow passing beyond a  
> heading
> limit. This makes sense in a normal org file and is very useful, but  
> when
> writing a presentation with org this restriction can get into the  
> way. This is
> not a big deal, but maybe others are also interested in this.
>
> - Darlan Cavalcante Moreira
>
> At Thu, 07 Jan 2010 09:41:29 +0100,
> Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
>>
>> Hi Carsten,
>>
>> Carsten Dominik wrote:
>>> On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
>>>> Carsten Dominik wrote:
>>>>> there is now a new option org-beamer-frame-default-options
>>>>
>>>> When setting it into Emacs, great, it DOES WORK as expected!
>>>>
>>>> Though, I believe this is more a setting of the document itself,  
>>>> instead of
>>>> one customization in my own `.emacs' file.
>>>>
>>>> I would rather like my colleagues to get the same output when  
>>>> compiling my
>>>> document. I tried, then, the following:
>>>>
>>>> --8<---------------cut here---------------start------------->8---
>>>> * COMMENT Setup
>>>>
>>>> # This is for the sake of Emacs.
>>>> # Local Variables:
>>>> # ispell-local-dictionary: "en_US"
>>>> # org-beamer-frame-default-options: "[allowframebreaks]"
>>>> # End:
>>>> --8<---------------cut here---------------end--------------->8---
>>>>
>>>> with no success, though.
>>>>
>>>> Maybe I would have to try with a `#+BIND'.
>>>
>>> #+BIND will do the trick, it was made just for this.
>>
>> #+BIND: org-beamer-frame-default-options "[allowframebreaks]"
>>
>> does work.
>>
>>
>>>> Though, wouldn't it be better to
>>>> explicitly add something like:
>>>>
>>>> --8<---------------cut here---------------start------------->8---
>>>> #+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
>>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> Yes, that would make sense if it is a frequently used feature.
>>> I like to hesitate with introducing these special customizations
>>> until I am convinced that this is used reasonably often.  Otherwise
>>> I would have to have 1000 of the special lines, approximately.
>>>
>>> Question to all:  How likely is the use of a default option you'd
>>> want to have on *every* frame?
>>
>> The problem is similar to the `fragile' option. Either we can  
>> detect the
>> "overflow" (and the automatically add the option only when needed),  
>> or we must
>> add it everywhere in order to ensure we won't have text cut.
>>
>> It's a bit different from when we directly edit beamer files. We  
>> compile often
>> and we see the problem appearing.
>>
>> Here, with Org, we would just work in Org only, and publish once at  
>> the end. A
>> bit more easy to be aware that some text may have pass away.
>>
>> As #+BIND works, I can imagine living quite honestly the way it  
>> currently is,
>> but I let the others decide upon this.
>>
>> Best regards,
>>  Seb
>>
>> -- 
>> Sébastien Vauban
>>
>>
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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

- Carsten

Re: [beamer] Order in preamble

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Jan 7, 2010, at 12:30 PM, Sébastien Vauban wrote:
>>
>> Another suggestion. I think the order of macros would be better changed in
>> the beamer preamble.
>
> OK, I have implemented that.  Please test it.

Perfectly working.

Thanks,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: New beamer support

[Sébastien Vauban]

Hi Carsten and Darlan,

Carsten Dominik wrote:
> On Jan 7, 2010, at 3:39 PM, Darlan Cavalcante Moreira wrote:
>>> Carsten Dominik wrote:
>>>> On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
>>>>> Carsten Dominik wrote:
>>>>>>
>>>>>> there is now a new option org-beamer-frame-default-options
>>>>>
>>>>> Though, wouldn't it be better to explicitly add something like:
>>>>>
>>>>> --8<---------------cut here---------------start------------->8---
>>>>> #+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
>>>>> --8<---------------cut here---------------end--------------->8---
>>>>
>>>> Yes, that would make sense if it is a frequently used feature. I like to
>>>> hesitate with introducing these special customizations until I am
>>>> convinced that this is used reasonably often. Otherwise I would have to
>>>> have 1000 of the special lines, approximately.
>>>>
>>>> Question to all: How likely is the use of a default option you'd want to
>>>> have on *every* frame?
>>>
>>> The problem is similar to the `fragile' option. Either we can detect the
>>> "overflow" (and the automatically add the option only when needed), or we
>>> must add it everywhere in order to ensure we won't have text cut.
>>>
>>> It's a bit different from when we directly edit beamer files. We compile
>>> often and we see the problem appearing.
>>>
>>> Here, with Org, we would just work in Org only, and publish once at the
>>> end. A bit more easy to be aware that some text may have pass away.
>>>
>>> As #+BIND works, I can imagine living quite honestly the way it currently
>>> is, but I let the others decide upon this.
>>
>> I don't think org-mode should try to detect when to use any of the frame
>> options in beamer. This could get into the way more then helping, specially
>> the allowframebreaks option.

I don't see what the problem could be of enabling (or having the possibility
to enable) that option on every slide by default.


>> In fact, the beamer manual tells you not to use the allowframebreaks option
>> except for long bibliographies (well, it also tells you not to use long
>> bibliographies) and I agree with this.

Just read page 56 of the beamer manual. Makes (some) sense, yes.


>> In a presentation you have to choose carefully what you will put in each
>> slide and always leaving this to beamer with the allowframebreaks is not a
>> good approach.

Still, I don't really see which problem this would bring, even if that's not
the purest manner of writing slides.

BTW, yes, I saw one problem. There is some orphan title on the bottom of one
page, and the contents on the top of the next one. Maybe, though, that can be
easily fixed by `nobreaks' macros (either manual or automatic).


>> In addition, I agree that when working in a presentation with org- mode you
>> compile much less, but you should still compile sometimes to see if the
>> slides are well designed.

That's really the point. Contents vs Presentation.

At least, my biggest problem is that I like to be warned somehow (but how?)
that such a problem is occurring, that some slide's contents is just too big
to stay on one page.

I would quite not like to have to scan the full presentation, comparing the
Org source and the beamer PDF in order to see if every line is in both. Don't
forget we can author such a presentation with multiple persons working on the
Org source, and that (as well) it's never always right or wrong: *changing of
theme* brings fonts differences or margins *differences that can hide lines
that were supposed to be visible*.

I basically understand your point, but my objection is about having constantly
to check the results for missing lines.


>> I don't know if Carsten has plans to implement this, but a "fast preview"
>> that exports and compiles only the current slide could be useful here.
>>
>> At last, I have a small feature request that would help organizing the
>> information among the slides. Right now you can use Alt+up/down arrow to
>> move a list item in a heading, but org does not allow passing beyond a
>> heading limit. This makes sense in a normal org file and is very useful,
>> but when writing a presentation with org this restriction can get into the
>> way. This is not a big deal, but maybe others are also interested in this.

Having to spend more time to move items from one slide to the other would make
such a feature useful for me as well, I guess.


> Do you also think I should not try to add the fragile option automatically?

Not sure if we can apply the above reasoning to that one. The question
certainly merits to be asked, but I'm not enlightened enough to give an
answer.

That's true that if we say: "it's up to the user" for the slide preparation,
we can apply that to everything, or consider the automatic stuff to be really
good.

Just don't know.

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: New beamer support

[Carsten Dominik]

On Jan 7, 2010, at 3:39 PM, Darlan Cavalcante Moreira wrote:

> At last, I have a small feature request that would help organizing the
> information among the slides. Right now you can use Alt+up/down  
> arrow to move a
> list item in a heading, but org does not allow passing beyond a  
> heading
> limit. This makes sense in a normal org file and is very useful, but  
> when
> writing a presentation with org this restriction can get into the  
> way. This is
> not a big deal, but maybe others are also interested in this.

I think that I cannot make this work in a good way.
Alternatives:

1. cut and paste of subtrees `C-c C-x C-w' ... `C-y'
2. Demote the frame line, move it down, promote it again.

- Carsten

Re: Re: New beamer support

[Darlan Cavalcante Moreira]

I agree that it is useful to have an easy way to specify one or more options for
every frame, but from the beamer manual I understand that these options where
created for specific cases and IMHO org shouldn't include any frame option by
default.

About the fragile option, the beamer manual tells you when to use it, but
doesn't mention any drawbacks of its use. I also tried searching for problems
with the fragile option but I found nothing and therefore I do not know the
implications of enabling the fragile option in every frame. However, if there is
no drawbacks then I wonder why the beamer author didn't make it the default
behavior.

Maybe it is better to ask in a beamer mailing list the implications of setting
this option for every frame.

- Darlan Cavalcante Moreira

At Thu, 07 Jan 2010 17:16:55 +0100,
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> 
> Hi Carsten and Darlan,
> 
> Carsten Dominik wrote:
> > On Jan 7, 2010, at 3:39 PM, Darlan Cavalcante Moreira wrote:
> >>> Carsten Dominik wrote:
> >>>> On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
> >>>>> Carsten Dominik wrote:
> >>>>>>
> >>>>>> there is now a new option org-beamer-frame-default-options
> >>>>>
> >>>>> Though, wouldn't it be better to explicitly add something like:
> >>>>>
> >>>>> --8<---------------cut here---------------start------------->8---
> >>>>> #+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
> >>>>> --8<---------------cut here---------------end--------------->8---
> >>>>
> >>>> Yes, that would make sense if it is a frequently used feature. I like to
> >>>> hesitate with introducing these special customizations until I am
> >>>> convinced that this is used reasonably often. Otherwise I would have to
> >>>> have 1000 of the special lines, approximately.
> >>>>
> >>>> Question to all: How likely is the use of a default option you'd want to
> >>>> have on *every* frame?
> >>>
> >>> The problem is similar to the `fragile' option. Either we can detect the
> >>> "overflow" (and the automatically add the option only when needed), or we
> >>> must add it everywhere in order to ensure we won't have text cut.
> >>>
> >>> It's a bit different from when we directly edit beamer files. We compile
> >>> often and we see the problem appearing.
> >>>
> >>> Here, with Org, we would just work in Org only, and publish once at the
> >>> end. A bit more easy to be aware that some text may have pass away.
> >>>
> >>> As #+BIND works, I can imagine living quite honestly the way it currently
> >>> is, but I let the others decide upon this.
> >>
> >> I don't think org-mode should try to detect when to use any of the frame
> >> options in beamer. This could get into the way more then helping, specially
> >> the allowframebreaks option.
> 
> I don't see what the problem could be of enabling (or having the possibility
> to enable) that option on every slide by default.
> 
> 
> >> In fact, the beamer manual tells you not to use the allowframebreaks option
> >> except for long bibliographies (well, it also tells you not to use long
> >> bibliographies) and I agree with this.
> 
> Just read page 56 of the beamer manual. Makes (some) sense, yes.
> 
> 
> >> In a presentation you have to choose carefully what you will put in each
> >> slide and always leaving this to beamer with the allowframebreaks is not a
> >> good approach.
> 
> Still, I don't really see which problem this would bring, even if that's not
> the purest manner of writing slides.
> 
> BTW, yes, I saw one problem. There is some orphan title on the bottom of one
> page, and the contents on the top of the next one. Maybe, though, that can be
> easily fixed by `nobreaks' macros (either manual or automatic).
> 
> 
> >> In addition, I agree that when working in a presentation with org- mode you
> >> compile much less, but you should still compile sometimes to see if the
> >> slides are well designed.
> 
> That's really the point. Contents vs Presentation.
> 
> At least, my biggest problem is that I like to be warned somehow (but how?)
> that such a problem is occurring, that some slide's contents is just too big
> to stay on one page.
> 
> I would quite not like to have to scan the full presentation, comparing the
> Org source and the beamer PDF in order to see if every line is in both. Don't
> forget we can author such a presentation with multiple persons working on the
> Org source, and that (as well) it's never always right or wrong: *changing of
> theme* brings fonts differences or margins *differences that can hide lines
> that were supposed to be visible*.
> 
> I basically understand your point, but my objection is about having constantly
> to check the results for missing lines.
> 
> 
> >> I don't know if Carsten has plans to implement this, but a "fast preview"
> >> that exports and compiles only the current slide could be useful here.
> >>
> >> At last, I have a small feature request that would help organizing the
> >> information among the slides. Right now you can use Alt+up/down arrow to
> >> move a list item in a heading, but org does not allow passing beyond a
> >> heading limit. This makes sense in a normal org file and is very useful,
> >> but when writing a presentation with org this restriction can get into the
> >> way. This is not a big deal, but maybe others are also interested in this.
> 
> Having to spend more time to move items from one slide to the other would make
> such a feature useful for me as well, I guess.
> 
> 
> > Do you also think I should not try to add the fragile option automatically?
> 
> Not sure if we can apply the above reasoning to that one. The question
> certainly merits to be asked, but I'm not enlightened enough to give an
> answer.
> 
> That's true that if we say: "it's up to the user" for the slide preparation,
> we can apply that to everything, or consider the automatic stuff to be really
> good.
> 
> Just don't know.
> 
> Best regards,
>   Seb
> 
> -- 
> Sébastien Vauban
> 
> 
> 
> _______________________________________________
> 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

Re: Re: New beamer support

[Carsten Dominik]

On Jan 7, 2010, at 7:03 PM, Darlan Cavalcante Moreira wrote:

>
> I agree that it is useful to have an easy way to specify one or more  
> options for
> every frame, but from the beamer manual I understand that these  
> options where
> created for specific cases and IMHO org shouldn't include any frame  
> option by
> default.
>
> About the fragile option, the beamer manual tells you when to use  
> it, but
> doesn't mention any drawbacks of its use. I also tried searching for  
> problems
> with the fragile option but I found nothing and therefore I do not  
> know the
> implications of enabling the fragile option in every frame. However,  
> if there is
> no drawbacks then I wonder why the beamer author didn't make it the  
> default
> behavior.

Because it is slow - each frame source code has to be written to a  
file, then read back in.

- Carsten

>
> Maybe it is better to ask in a beamer mailing list the implications  
> of setting
> this option for every frame.
>
> - Darlan Cavalcante Moreira
>
> At Thu, 07 Jan 2010 17:16:55 +0100,
> Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
>>
>> Hi Carsten and Darlan,
>>
>> Carsten Dominik wrote:
>>> On Jan 7, 2010, at 3:39 PM, Darlan Cavalcante Moreira wrote:
>>>>> Carsten Dominik wrote:
>>>>>> On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
>>>>>>> Carsten Dominik wrote:
>>>>>>>>
>>>>>>>> there is now a new option org-beamer-frame-default-options
>>>>>>>
>>>>>>> Though, wouldn't it be better to explicitly add something like:
>>>>>>>
>>>>>>> --8<---------------cut here---------------start------------- 
>>>>>>> >8---
>>>>>>> #+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
>>>>>>> --8<---------------cut here---------------end--------------- 
>>>>>>> >8---
>>>>>>
>>>>>> Yes, that would make sense if it is a frequently used feature.  
>>>>>> I like to
>>>>>> hesitate with introducing these special customizations until I am
>>>>>> convinced that this is used reasonably often. Otherwise I would  
>>>>>> have to
>>>>>> have 1000 of the special lines, approximately.
>>>>>>
>>>>>> Question to all: How likely is the use of a default option  
>>>>>> you'd want to
>>>>>> have on *every* frame?
>>>>>
>>>>> The problem is similar to the `fragile' option. Either we can  
>>>>> detect the
>>>>> "overflow" (and the automatically add the option only when  
>>>>> needed), or we
>>>>> must add it everywhere in order to ensure we won't have text cut.
>>>>>
>>>>> It's a bit different from when we directly edit beamer files. We  
>>>>> compile
>>>>> often and we see the problem appearing.
>>>>>
>>>>> Here, with Org, we would just work in Org only, and publish once  
>>>>> at the
>>>>> end. A bit more easy to be aware that some text may have pass  
>>>>> away.
>>>>>
>>>>> As #+BIND works, I can imagine living quite honestly the way it  
>>>>> currently
>>>>> is, but I let the others decide upon this.
>>>>
>>>> I don't think org-mode should try to detect when to use any of  
>>>> the frame
>>>> options in beamer. This could get into the way more then helping,  
>>>> specially
>>>> the allowframebreaks option.
>>
>> I don't see what the problem could be of enabling (or having the  
>> possibility
>> to enable) that option on every slide by default.
>>
>>
>>>> In fact, the beamer manual tells you not to use the  
>>>> allowframebreaks option
>>>> except for long bibliographies (well, it also tells you not to  
>>>> use long
>>>> bibliographies) and I agree with this.
>>
>> Just read page 56 of the beamer manual. Makes (some) sense, yes.
>>
>>
>>>> In a presentation you have to choose carefully what you will put  
>>>> in each
>>>> slide and always leaving this to beamer with the allowframebreaks  
>>>> is not a
>>>> good approach.
>>
>> Still, I don't really see which problem this would bring, even if  
>> that's not
>> the purest manner of writing slides.
>>
>> BTW, yes, I saw one problem. There is some orphan title on the  
>> bottom of one
>> page, and the contents on the top of the next one. Maybe, though,  
>> that can be
>> easily fixed by `nobreaks' macros (either manual or automatic).
>>
>>
>>>> In addition, I agree that when working in a presentation with  
>>>> org- mode you
>>>> compile much less, but you should still compile sometimes to see  
>>>> if the
>>>> slides are well designed.
>>
>> That's really the point. Contents vs Presentation.
>>
>> At least, my biggest problem is that I like to be warned somehow  
>> (but how?)
>> that such a problem is occurring, that some slide's contents is  
>> just too big
>> to stay on one page.
>>
>> I would quite not like to have to scan the full presentation,  
>> comparing the
>> Org source and the beamer PDF in order to see if every line is in  
>> both. Don't
>> forget we can author such a presentation with multiple persons  
>> working on the
>> Org source, and that (as well) it's never always right or wrong:  
>> *changing of
>> theme* brings fonts differences or margins *differences that can  
>> hide lines
>> that were supposed to be visible*.
>>
>> I basically understand your point, but my objection is about having  
>> constantly
>> to check the results for missing lines.
>>
>>
>>>> I don't know if Carsten has plans to implement this, but a "fast  
>>>> preview"
>>>> that exports and compiles only the current slide could be useful  
>>>> here.
>>>>
>>>> At last, I have a small feature request that would help  
>>>> organizing the
>>>> information among the slides. Right now you can use Alt+up/down  
>>>> arrow to
>>>> move a list item in a heading, but org does not allow passing  
>>>> beyond a
>>>> heading limit. This makes sense in a normal org file and is very  
>>>> useful,
>>>> but when writing a presentation with org this restriction can get  
>>>> into the
>>>> way. This is not a big deal, but maybe others are also interested  
>>>> in this.
>>
>> Having to spend more time to move items from one slide to the other  
>> would make
>> such a feature useful for me as well, I guess.
>>
>>
>>> Do you also think I should not try to add the fragile option  
>>> automatically?
>>
>> Not sure if we can apply the above reasoning to that one. The  
>> question
>> certainly merits to be asked, but I'm not enlightened enough to  
>> give an
>> answer.
>>
>> That's true that if we say: "it's up to the user" for the slide  
>> preparation,
>> we can apply that to everything, or consider the automatic stuff to  
>> be really
>> good.
>>
>> Just don't know.
>>
>> Best regards,
>>  Seb
>>
>> -- 
>> Sébastien Vauban
>>
>>
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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

- Carsten

Re: New beamer support

[Sébastien Vauban]

Hi Darlan,

Darlan Cavalcante Moreira wrote:
> I agree that it is useful to have an easy way to specify one or more options
> for every frame, but from the beamer manual I understand that these options
> where created for specific cases and IMHO org shouldn't include any frame
> option by default.

I don't think I (or we) said it should be that way by default. My "request" is
just to be sure we have a manner to tell Org so.

I proposed an explicit meta-tag for the whole Org document, but the BIND
meta-tag option is good for me, as long as it does not disappear! ;-)


> About the fragile option, the beamer manual tells you when to use it, but
> doesn't mention any drawbacks of its use. I also tried searching for
> problems with the fragile option but I found nothing and therefore I do not
> know the implications of enabling the fragile option in every frame.
> However, if there is no drawbacks then I wonder why the beamer author didn't
> make it the default behavior.
>
> Maybe it is better to ask in a beamer mailing list the implications of
> setting this option for every frame.

As said by Carsten, reason is performance...

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode