From: Daniele Pizzolli <dan@toel.it>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: dates in heading break beamer export
Date: Mon, 30 Sep 2013 18:02:51 +0200 [thread overview]
Message-ID: <5249A0AB.7080408@toel.it> (raw)
In-Reply-To: <20130929172751.4644b537@aga-netbook>
On 09/29/2013 05:27 PM, Marcin Borkowski wrote:
> Dnia 2013-09-29, o godz. 16:53:14
> Nicolas Goaziou:
[]
>> It's a LaTeX Beamer problem: it doesn't like
>>
>> \section{title \textit{[2013-09-29 Sun]}}
>>
>> produced by Org, although regular LaTeX accepts it.
>>
>> Do you know about a workaround for this?
Not really.
> This is really a workaround: put a \protect before \textit.
Or why not drop \textit?
> In general, putting formatting commands in \section title etc., even if
> not erroneous, is considered a bad practice.
But org-mode allow this!
I think that if something is allowed in org-mode syntax but not by the
underlining tools used for export, the exporter should take care to find
a suitable workaround.
I just found that the same problem (work in latex, does not work in
beamer) exists for footnotes in header!
A feature request would be to have some checks on org files a la
flymake, at least for common potential sources of problems that
usually break the export like:
- missing two empty lines after footnotes
- missing empty line after RESULTS:
- =string=[footnote]
Maybe something already exists and I am simply not aware.
Regards,
Daniele
next prev parent reply other threads:[~2013-09-30 16:03 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 [this message]
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
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=5249A0AB.7080408@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).