From: Matthew Lundin <mdl@imapmail.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: footnote renumber bug
Date: Thu, 02 Jul 2009 16:53:34 -0500 [thread overview]
Message-ID: <874otuwy3l.fsf@fastmail.fm> (raw)
In-Reply-To: <4A4D13E2.5060707@easy-emacs.de> ("Andreas Röhler"'s message of "Thu, 02 Jul 2009 22:09:06 +0200")
Hi Andreas,
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> Matthew Lundin wrote:
>> Footnote.el, by contrast, was designed for short email messages in which
>> there is no distinction between source text and exported text. Though it
>> serves this limited purpose admirably, it offers only a very rudimentary
>> numbering system rather than a complete markup solution. For any complex
>> writing (e.g., a research paper with dozens of footnotes), footnote.el
>> is well-nigh impossible to use. There are simply too many chances of
>> broken or mixed up links.
>>
>
> Ignoring the guts of org-modes footnote implementation, just my impression
> of footnote.el:
>
> it's fine by architecture and --if patched-- well capable for all things
> you want to do with footnotes.
> Can't see any limitation concerning larger texts.
> It simply wasn't --or isn't-- written to the end.
Thanks for the clarification. Reading over my email, I believe I may
stated some conclusions about footnote.el too strongly. What I should
have said is that *in my own experience* I have found footnote.el
difficult to use (in its pre-patched form, of course).
Try as I might, I could never get Footnote-renumber-footnotes to do
anything. And if I moved any footnotes in the original text, deleted
them manually, or reopened a document with footnotes,
Footnote-add-footnote behaved unpredictably, creating duplicate numbers,
skipping numbers, putting footnotes in the wrong order, placing
footnotes randomly above and below the "Footnotes:" line, etc.
Very likely, my issues with footnote.el were due to my own lack of
understanding of its mechanics, and I can see how your patch fixes
things up quite a bit. It will be a really nice contribution to emacs if
footnote.el is fixed, since modes such as Muse rely on it.
Also, my apologies for a somewhat wordy defense of org-footnote. I wrote
it only because I am a very big fan. :)
Regards,
Matt
next prev parent reply other threads:[~2009-07-02 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 6:55 footnote renumber bug Andreas Roehler
2009-07-02 11:44 ` Karl Maihofer
2009-07-02 13:18 ` Andreas Röhler
2009-07-02 15:48 ` Matthew Lundin
2009-07-02 16:05 ` Matthew Lundin
2009-07-02 20:09 ` Andreas Röhler
2009-07-02 21:53 ` Matthew Lundin [this message]
2009-07-03 8:36 ` Scot Becker
2009-07-03 12:08 ` Andreas Röhler
2009-07-03 14:17 ` Paul R
2009-07-03 14:51 ` Andreas Röhler
2009-07-03 14:42 ` Matthew Lundin
2009-07-03 21:49 ` Carsten Dominik
2009-07-04 8:02 ` Andreas Roehler
2009-07-04 20:30 ` Matthew Lundin
2009-07-05 20:31 ` Carsten Dominik
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=874otuwy3l.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=andreas.roehler@easy-emacs.de \
--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).