emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Fabrice Popineau <fabrice.popineau@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: ox-beamer and CUSTOM_ID
Date: Thu, 15 Oct 2015 18:54:48 +0200	[thread overview]
Message-ID: <CAFgFV9Mp3gT2QR=RkjKqkTY6bU0C9TotmSjkzMMqaZyzzbmisg@mail.gmail.com> (raw)
In-Reply-To: <87wpuowmrn.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]

2015-10-15 10:37 GMT+02:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:

> Fabrice Popineau <fabrice.popineau@gmail.com> writes:
>
> > At some point LaTeX reported an error on some frame heading.
> > I wrongly inferred it could be the label.
>
> It would be nice to investigate about this error, it it persists.
>
>
Beamer is very bad at reporting errors at their true origin.

Actually, I had 2 errors.

First all my Org->TeX files use Babel, and they doesn't seem to cope well
with colons in labels.
(org-lint even reports about it)
Unfortunately, the default naming scheme for internal labels is using
colons.
Hence I wanted to use my own labels.

(Actually, I don't understand what prevents "beamer 2015/01/05 3.36" to use
colons in
labels. I thought that this problem has been solved around beamer 3.30.)

The other error was elsewhere in the slide and it is a separate issue.
Actually I had A_{}_{i+1} somewhere. Unfortunately, it is quite easy to
enter such stuff
in Org mode with the right edit sequence (I need to pick this sequence and
report about it).
When the result is displayed (well, at least in my setup), you don't see
the double
subscript any more. It is displayed the same way A_{i+1} is.
You need to erase everything and retype it. Or turn off the sub/superscript
option (?).

Anyway, now "ox-beamer" should obey to `org-latex-prefer-user-labels'
> for custom ID.
>

Thanks!

Regards,

Fabrice

[-- Attachment #2: Type: text/html, Size: 2442 bytes --]

  reply	other threads:[~2015-10-15 16:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 11:24 ox-beamer and CUSTOM_ID Fabrice Popineau
2015-10-13 19:26 ` Nicolas Goaziou
2015-10-13 19:38   ` Fabrice Popineau
2015-10-13 19:50     ` Nicolas Goaziou
2015-10-13 19:58       ` Fabrice Popineau
2015-10-13 20:52         ` Nicolas Goaziou
2015-10-13 21:12           ` Fabrice Popineau
2015-10-13 22:18             ` Nicolas Goaziou
2015-10-14  9:47               ` Fabrice Popineau
2015-10-14 11:57                 ` Nicolas Goaziou
2015-10-14 12:18                   ` Fabrice Popineau
2015-10-15  8:37                     ` Nicolas Goaziou
2015-10-15 16:54                       ` Fabrice Popineau [this message]
2015-10-15 19:25                         ` Fabrice Popineau
2015-10-15 19:48                           ` Nicolas Goaziou
2015-10-15 20:20                             ` Fabrice Popineau
2015-10-16 20:59                               ` Nicolas Goaziou

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='CAFgFV9Mp3gT2QR=RkjKqkTY6bU0C9TotmSjkzMMqaZyzzbmisg@mail.gmail.com' \
    --to=fabrice.popineau@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).