From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Adventures with org-footnote-auto-adjust
Date: Mon, 25 Feb 2013 05:56:55 -1000 [thread overview]
Message-ID: <m1liac9yk8.fsf@tsdye.com> (raw)
In-Reply-To: <87wqtwslyh.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 25 Feb 2013 11:54:14 +0100")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> I've learned that there are certain conditions (I don't know how many)
>> where the space after a sentence won't accept a footnote insertion.
>
> There shouldn't be any of such conditions.
Great. I'll be on the lookout and will report when I find them.
>
>> The example sentence is one of these. Apparently, it is the `~.'
>> combination that triggers the condition. Org is good enough to
>> prohibit inserting a new footnote into one of these "black holes"
>> (which is how I discovered them), but it doesn't mind if I cut and
>> paste a footnote into one.
>
> I fixed it. Footnote references should be allowed there.
Yes, I can confirm that this is fixed. Thanks!
>
>> I'm not certain how much mischief this might have caused. I discovered
>> the problem when the text of *both* footnotes in a section of the
>> document were incorrect.
>>
>> In my case, org-footnote-auto-adjust doesn't perform any crucial
>> function--it just makes the Org mode buffer seem more orderly. Given
>> that there are "black holes" in the buffer, whose presence have the
>> ability to confuse org-footnote-auto-adjust so that data are lost,
>> should org-footnote-auto-adjust be deprecated?
>
> `org-footnote-auto-adjust' still does its job when, for example, a new
> footnote is created or a footnote is deleted. It is fragile when
> copy-pasting a footnote reference across some text.
>
In my case, the intended effects of `org-footnote-auto-adjust' were
purely cosmetic in the Org buffer and didn't affect the output. Is
there a situation where it does something that has an effect on output?
> Anyway, it should be possible to fix most of these "black holes", if
> only we are aware of them.
OK. Apologies for the graphic term. I hope it didn't offend. Dismay got
the better of tact, I think.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2013-02-25 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 18:09 Adventures with org-footnote-auto-adjust Thomas S. Dye
2013-02-25 10:54 ` Nicolas Goaziou
2013-02-25 15:56 ` Thomas S. Dye [this message]
2013-02-25 16:06 ` Nicolas Goaziou
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=m1liac9yk8.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).