Nicolas Goaziou n.goaz...@gmail.com writes:
Should there be a check in the exporter, for latex based backends, if
the document class expected is not defined? This would have made things
a lot quicker to resolve in this case!
What is an expected document class? Beamer export can happen with
Rasmus ras...@gmx.us writes:
There is the #+LATEX_HEADER:. Is a keyword specific to Beamer
required? It would by symmetric with #+BEAMER: but I have never
needed it before.
Something like
#+LATEX_HEADER:\AtBeginSection[]{\frame{\thispagestyle{empty}\tableofcontents[currentsection]}}
is
Should there be a check in the exporter, for latex based backends, if
the document class expected is not defined? This would have made things
a lot quicker to resolve in this case!
What is an expected document class? Beamer export can happen with
a beamer or an article (and probably others)
Hi,
LaTeX class is never unspecified because `beamer' back-end is
a derivative of `latex', and, as such, `org-latex-default-class' will be
used. `beamer' could specify its own default class, but that class would
still need to be defined in `org-latex-classes'.
Sure, it should be in the
Vincent Beffara vbeffara...@gmail.com writes:
Sure, it should be in the default list. What is the drawback?
The default list is defined in ox-latex.el, which doesn't know anything
about ox-beamer.el. The drawback is that it doesn't seem clean to me.
I think it's better to make it a fallback
Nicolas Goaziou n.goaz...@gmail.com writes:
If the author is cautious about keywords used (i.e. #+BEAMER: or
#+LATEX:), it should be possible to export the same document with either
`beamer' or `latex' back-end. Though, I don't know how much difference
there would be between the output from
Hello,
Rasmus ras...@gmx.us writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
If the author is cautious about keywords used (i.e. #+BEAMER: or
#+LATEX:), it should be possible to export the same document with either
`beamer' or `latex' back-end. Though, I don't know how much difference
Nicolas,
There is the #+LATEX_HEADER:. Is a keyword specific to Beamer
required? It would by symmetric with #+BEAMER: but I have never
needed it before.
Something like
#+LATEX_HEADER:\AtBeginSection[]{\frame{\thispagestyle{empty}\tableofcontents[currentsection]}}
is not interesting to a
James Harkins jamshar...@gmail.com writes:
Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
Never use the passive [voice] where you can use the active.)
I prefer alert. See the Beamer manual (texdoc beamer in texlive) on
change of style and how to use alert (e.g. alert
On Wed, Feb 06, 2013 at 01:32:22PM +0100, Rasmus wrote:
I don't know how hard it would be to make the default block (of
level 3, say) a list block, but I guess that's ultimately what you
want? Such a behavior shouldn't be the default, IMO, since a headline
is not a list.
Nested headlines
Hi Rasmus,
Rasmus wrote:
James Harkins jamshar...@gmail.com writes:
Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
Never use the passive [voice] where you can use the active.)
I prefer alert. See the Beamer manual (texdoc beamer in texlive) on
change of style and
Hello,
Eric S Fraga e.fr...@ucl.ac.uk writes:
Taking your updated version of the example document, I cannot get the
exporter to generate a latex file that will compile because it is
missing a documentclass directive. Is there something else that needs
to be configured to support beamer, as
James Harkins jamshar...@gmail.com writes:
Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
Never use the passive [voice] where you can use the active.)
Obviously, me, as the author of the back-end. Org offers only one slot
for strong emphasis. I had to choose between
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Eric S Fraga e.fr...@ucl.ac.uk writes:
Taking your updated version of the example document, I cannot get the
exporter to generate a latex file that will compile because it is
missing a documentclass directive. Is there something else that
On Feb 7, 2013 3:57 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
Never use the passive [voice] where you can use the active.)
Obviously, me, as the author of the back-end. Org offers only one slot
for strong
On Tue, Feb 5, 2013 at 3:21 PM, Nick Dokos nicholas.do...@hp.com wrote:
I added a beamer entry to org-e-latex-classes as indicated in
http://thread.gmane.org/gmane.emacs.orgmode/61497/focus=61536
(again, I
have no idea if the sectioning stuff matters or not, and whether it leads
to
Nick Dokos nicholas.do...@hp.com writes:
[...]
Customizing org-e-beamer-environments-extra should do the trick. I was
Nick,
thanks for this. This hint led me to org-e-beamer-select-environment
which, after binding to a key, has allowed me to play sufficiently
enough with the new exporter
Nicolas Goaziou n.goaz...@gmail.com writes:
[...]
Here's an excerpt from ox-beamer.el documentation:
;; - Headlines become frames when their level is equal to
;; `org-beamer-frame-level' (or H value in the OPTIONS line).
Nicolas,
I have decided to bite the bullet and try to get all of
Hi James,
James Harkins wrote:
3. Strong *emphasis* now renders in red, instead of keeping the text's
original color and switching to boldface.
That's because the * are exported as \alert macros in the new exporter
(instead of \textbf in the old one -- for bold face).
As, in the LaTeX's
James Harkins jamshar...@gmail.com wrote:
...
I get the feeling here that the new beamer exporter was written
without a lot of real-world user requirements. Certainly, it's
understandable that HTML, LaTeX article-style and ODT exporters would
be more widely used and more important to get
Hello,
Eric S Fraga e.fr...@ucl.ac.uk writes:
I have decided to bite the bullet and try to get all of my beamer files
working with the new exporter. I have started simply with the
presentation.org file that I had put on Worg for the tutorial on beamer
for the old exporter.
A truncated
Hello,
I'm attaching an org file that illustrates a couple of the beamer
formatting options that I used a lot in the old exporter.
See below.
1. I *did* use the block environment to emphasize some text by pulling
it out of the itemize bullet lists. If I customize blockenv in org
to render
Nicolas Goaziou n.goaz...@gmail.com writes:
[...]
I have attached the simple test file.
Where am I going wrong? If I change H:2 to H:1, it works although
obviously the output is not what I want. Have I misunderstand something
rather fundamental?
I have no problem exporting this file.
Nicolas Goaziou n.goaz...@gmail.com writes:
[...]
Let's start slowly. I think you can get how to make the changes yourself
with a couple of examples. Since you seem to like lists (you know that
Till Tantau frowns upon the use of third level lists in presentations,
don't you?), the first rule
Thanks for all this. I'll look at the new org markup later today. That
should help a lot.
On Feb 6, 2013 3:03 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
3. Strong *emphasis* now renders in red, instead of keeping the text's
original color and switching to boldface.
Indeed. Strong
James Harkins jamshar...@gmail.com writes:
[...]
Ok. There was something about customizing this on the list just recently.
I'll use that. (FWIW, I had to produce a number of *gasp cough choke*
PowerPoint shows in my previous job, and they told us not to use red for
*anything* unless it
Suvayu Ali fatkasuvayu+linux at gmail.com writes:
On Mon, Feb 04, 2013 at 12:00:08PM +0800, James Harkins wrote:
#+OPTIONS: H:10 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
The H:10 is your problem. Since you want 2nd level headlines to be
frames, it should be H:2.
Ah. OK, that's
Hello,
James Harkins jamshar...@gmail.com writes:
Suvayu Ali fatkasuvayu+linux at gmail.com writes:
On Mon, Feb 04, 2013 at 12:00:08PM +0800, James Harkins wrote:
#+OPTIONS: H:10 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
The H:10 is your problem. Since you want 2nd level
On Feb 5, 2013 3:51 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
In particular, All frames children become block environments. So in
your example Third-level is a block environment and Fourth-level is
a block within it. There's no flattening going on (look at the tex file
to convince
James Harkins jamshar...@gmail.com wrote:
On Feb 5, 2013 3:51 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
In particular, All frames children become block environments. So in
your example Third-level is a block environment and Fourth-level is
a block within it. There's no flattening
During the semester break, I want to switch over to the new exporter.
Currently I'm using export mainly for beamer presentations.
I found the org-e-latex-classes entry in an old e-mail post. With
that, M-x org-export-dispatch l P produces a .tex document that
compiles. But the output is not
On Mon, Feb 04, 2013 at 12:00:08PM +0800, James Harkins wrote:
#+OPTIONS: H:10 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
The H:10 is your problem. Since you want 2nd level headlines to be
frames, it should be H:2.
Hope this helps,
--
Suvayu
Open source is the future. It sets us
32 matches
Mail list logo
