emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Beamer export: one question and one bug
Date: Sat, 26 Oct 2013 21:31:23 -0400	[thread overview]
Message-ID: <87hac3lct0.fsf@gmail.com> (raw)
In-Reply-To: 87ob6cts64.fsf@syk.fi

Jarmo Hurri <jarmo.hurri@syk.fi> writes:

> Greetings!
>
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>>> 1. First the question: when I export the org file below as Beamer (C-c
>>>    C-e l O), I get an empty outline. How do I fix this?
>>
>> I cannot reproduce it. What happens with "-q"?
>
> The same thing: an empty outline.
>

Seems to work fine for me with the older version that I was running,
but I upgraded to latest and I get the beamer presentation I expected.

> To be exact, I ran "emacs -q" and the executed the following commands
> before loading the org-file, in order to use the newest version of org:
>
> (setq load-path (cons "/home/jarmo/addons/emacs-packages/org/lisp" load-path))
> (require 'org)
> (require 'ox-beamer)
>
> Maybe this is related to TeX version? Mine is
>
> TeX 3.1415926 (TeX Live 2013)
>

My TeX says 

This is TeX, Version 3.1415926 (TeX Live 2009/Debian)

but I don't know whether that explains it.

>>> 2. Then the bug. If you remove the comment character in the second
>>>    slide, Beamer export gives an error, while a regular LaTeX export
>>>    (C-c C-e l o) produced output.
>> The export process doesn't unencode hexified links, so the problem
>> doesn't come from the equality sign but from the percent one.
>
> Ok.
>
>> This problem was discussed recently (look for a thread named "Encoding
>> Problem in export?" on the ML), but, IIRC, no solution was found.
>
> I will read through the thread, but at the moment I don't understand why
> the Beamer export behaves differently than the regular LaTeX export.
>

Export to Latex produces

\section{And this is the second slide}
\label{sec-2}
\begin{itemize}
\item with one commented item\ldots{}
\item \ldots{} containing a \href{https://www.google.com/#q%3Dorg%2Bmode}{link} that will amaze the reader
\end{itemize}

Export to beamer produces

\begin{frame}[label=sec-2]{And this is the second slide}
\begin{itemize}
\item with one commented item\ldots{}
\item \ldots{} containing a \href{https://www.google.com/#q%3Dorg%2Bmode}{link} that will amaze the reader
\end{itemize}
\end{frame}

so the link is treated exactly the same in the two cases. Probably the
enclosing environment (\section vs \frame) is what causes the different
behavior.
-- 
Nick

next prev parent reply	other threads:[~2013-10-27  1:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 11:58 Beamer export: one question and one bug Jarmo Hurri
2013-10-25 18:56 ` Nicolas Goaziou
2013-10-26  7:20   ` Jarmo Hurri
2013-10-27  1:31     ` Nick Dokos [this message]
2013-10-27  9:10       ` Jarmo Hurri
2013-10-28 14:13         ` Nick Dokos
2013-11-02 14:10           ` Ista Zahn
2013-11-03 10:06             ` Jarmo Hurri
2013-11-03 14:18               ` Ista Zahn
2013-11-03 16:13                 ` Jarmo Hurri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hac3lct0.fsf@gmail.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).