From: Jambunathan K <firstname.lastname@example.org>
Subject: Re: [BUG] crash while ping-ponging between back-to-back footnotes.
Date: Wed, 29 Jun 2011 19:41:15 +0530 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Bastien's message of "Wed, 29 Jun 2011 15:26:39 +0200")
Bastien <email@example.com> writes:
> Hi Jambunathan,
> Jambunathan K <firstname.lastname@example.org> writes:
>> Summary: Sample org file down below also doubles up as bug report.
>> * Sample
>> Add footnote-1 using C-c C-x f [fn:1][fn:2]
> Workaround: separate the footnotes with a space.
> Add footnote-1 using C-c C-x f [fn:1] [fn:2]
> Both fontification and export get confused if footnotes are not
> separated with a space -- I think it's okay to live with this
> one-space-between-footnotes policy, but I let Nicolas decides.
Since [fn:2] is automagically added by C-c C-x f may be it can check for
an immediately preceding footnote and DTRT (inserting space or whatever
the preference is) if it is not done already.
> Thanks for reporting this,
next prev parent reply other threads:[~2011-06-29 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 11:48 Jambunathan K
2011-06-29 12:28 ` Nicolas Goaziou
2011-06-29 12:52 ` Jambunathan K
2011-06-29 13:26 ` Bastien
2011-06-29 14:11 ` Jambunathan K [this message]
2011-06-29 17:41 ` Nicolas Goaziou
2011-06-30 8:29 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).