>>> "ESF" == Eric S Fraga writes:
> On Friday, 16 Oct 2020 at 18:06, Uwe Brauer wrote:
>> I think I have to learn more about that.
> A good starting point to learn what is possible in org for beamer export
> is to turn on beamer mode:
> #+startup: beamer
> This provides, in particular, one key
On Friday, 16 Oct 2020 at 18:06, Uwe Brauer wrote:
> I think I have to learn more about that.
A good starting point to learn what is possible in org for beamer export
is to turn on beamer mode:
#+startup: beamer
This provides, in particular, one key binding (C-c C-b) which allows you
to change t
>>> "ESF" == Eric S Fraga writes:
> On Thursday, 15 Oct 2020 at 19:44, Uwe Brauer wrote:
>> How can I avoid this annoying block environment?
> I know you have sort of solved this (by promoting the headline to a
> higher level) but the question I would have asked is: what did you want
> the expor
On Thursday, 15 Oct 2020 at 19:44, Uwe Brauer wrote:
> How can I avoid this annoying block environment?
I know you have sort of solved this (by promoting the headline to a
higher level) but the question I would have asked is: what did you want
the export engine to do with a subheading?
In beamer,
>>> "CB" == Colin Baxter writes:
>> Uwe Brauer writes:
>> Hello I have a org file that I want to export either to
>> 1. Regular latex or
>> 2. To beamer.
>> So I just use the corresponding export engines.
>> However the following minimal example puzzles me:
>> #+begin_src
>> # -*- org
> Uwe Brauer writes:
> Hello I have a org file that I want to export either to
> 1. Regular latex or
> 2. To beamer.
> So I just use the corresponding export engines.
> However the following minimal example puzzles me:
> #+begin_src
> # -*- org-confi
