From: Daniele Pizzolli <dan@toel.it>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: dates in heading break beamer export
Date: Wed, 02 Oct 2013 17:36:55 +0200 [thread overview]
Message-ID: <524C3D97.60705@toel.it> (raw)
In-Reply-To: <87d2nnu6pp.fsf@gmail.com>
On 10/02/2013 03:45 PM, Nicolas Goaziou wrote:
> Hello,
>
> Daniele Pizzolli writes:
>
>> In fact I use org-mode primarily to stay away from *tex
>> nuisances... and I think that I am not the only one. I know enough
>> latex to find a workaround myself (not enough to offer a general
>> reliable solution) but I do not think that this will be a pleasant
>> experience for a newcomer or to somebody that choose org-mode for the
>> latex export capability.
>
> Fair enough. What, exactly, do you suggest as generated LaTeX code?
Thanks Nicolas for following my arguments.
> IIUC, you want to drop any markup for timestamps when located in
> a headline, ignoring `org-latex-active-timestamp-format' and al. Am
> I missing something else?
Yes, I think is fair to drop the markup. I would also think that this
is safe default when nested markup is bad.
Maybe the exporter can emit a notice/warning.
> BTW, the =verbatim=[fn:1] case is unrelated to export. See
> `org-emphasis-regexp-components'.
Yes, sorry, I mixed two not-so-related problem. The beamer exporter do not
work with this code:
#+OPTIONS: H:3
* title test[fn:1]
** section
*** subsection
[fn:1] text
The output is:
org-latex-compile: PDF file ./beamer-bug-footnote.pdf wasn't produced: [undefined control sequence] Runaway argument
The =verbatim=[fn:1] problem was discovered trying to find a
workaround for the footnotes in the headers...
Oh, in fact searching emphasis + footnote lead to some results.
The question hit this list periodically... so maybe it’s worth
documenting it better. I will try found a general answer and
propose a patch for the docs.
It seems that I am going to drop latex nuisances to go into elisp
ones ;-)
Thanks again,
Daniele
next prev parent reply other threads:[~2013-10-02 15:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 10:33 Bug: dates in heading break beamer export Daniele Pizzolli
2013-09-29 14:53 ` Nicolas Goaziou
2013-09-29 15:27 ` Marcin Borkowski
2013-09-30 16:02 ` Daniele Pizzolli
2013-09-30 17:05 ` Marcin Borkowski
2013-10-01 16:01 ` Nicolas Goaziou
2013-10-01 16:33 ` Marcin Borkowski
2013-10-02 6:50 ` Bug: code and footnotes (was Bug: dates in heading break beamer export) Daniele Pizzolli
2013-10-01 8:09 ` Bug: dates in heading break beamer export Eric S Fraga
2013-10-02 6:47 ` Daniele Pizzolli
2013-10-02 13:45 ` Nicolas Goaziou
2013-10-02 15:36 ` Daniele Pizzolli [this message]
2013-10-02 15:55 ` Nicolas Goaziou
2013-10-02 16:10 ` Daniele Pizzolli
2013-10-02 20:47 ` Marcin Borkowski
2013-10-03 13:30 ` Nicolas Goaziou
2013-10-03 15:59 ` Daniele Pizzolli
2013-10-04 19:17 ` Nicolas Goaziou
2013-10-02 22:12 ` Suvayu Ali
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=524C3D97.60705@toel.it \
--to=dan@toel.it \
--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).