From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: dates in heading break beamer export
Date: Thu, 3 Oct 2013 00:12:42 +0200 [thread overview]
Message-ID: <20131002221242.GV2622@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <8761tfu0ov.fsf@gmail.com>
On Wed, Oct 02, 2013 at 05:55:44PM +0200, Nicolas Goaziou wrote:
> Daniele Pizzolli <dan@toel.it> writes:
>
> > Yes, I think is fair to drop the markup.
>
> OK.
>
> > I would also think that this is safe default when nested markup is
> > bad.
>
> Do you have an exhaustive list of such cases?
>
> > Maybe the exporter can emit a notice/warning.
>
> That it dropped the markup?
>
> > 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
>
> Of course, that's a similar problem: footnotes are not allowed in
> headlines. Though, in this case, it isn't possible to drop the markup.
> What LaTeX code do you suggest?
Strange, it seems to work for me.
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2013-10-02 22:12 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
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 [this message]
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=20131002221242.GV2622@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@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).