From: Lawrence Mitchell <email@example.com>
Subject: Re: [PATCH] org-latex: Don't append newline to end of footnote
Date: Wed, 30 Mar 2011 10:14:05 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
> Lawrence Mitchell <email@example.com> writes:
> The analysis is good, but unfortunately the patch has a flaw.
> In fact, your patch work in that particular situation, but not if
> a footnote definition ends with a list, nor if it ends with a link. To
> solve the latter, you need to insert a white-space before the closing
> bracket. To solve the former, I thought adding a newline instead of the
> white-space was enough, but it now appears it was a bad idea.
> Thus, the solution lies elsewhere.
Ugh, indeed. I wonder whether it would be enough to add the
correct list indent to the beginning of the line with the closing
ALthough I notice without my patch, the export of a footnote
containing a list which is in a list also does not work:
- Hello [fn:1]
- an item
No idea how to fix this though, sorry.
Lawrence Mitchell <firstname.lastname@example.org>
next prev parent reply other threads:[~2011-03-30 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 13:09 [BUG] LaTeX export inserts "ORG-LIST-END-MARKER" Rainer M Krug
2011-03-29 14:20 ` [PATCH] org-latex: Don't append newline to end of footnote Lawrence Mitchell
2011-03-29 17:38 ` Nicolas
2011-03-30 7:49 ` Rainer M Krug
2011-03-30 9:14 ` Lawrence Mitchell [this message]
2011-03-30 14:46 ` Rainer M Krug
2011-03-30 22:06 ` Nicolas
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).