Hello,

Jorge <jorge13...@gmail.com> writes:

> Start Emacs with an empty init file and make the following customizations:
>
> - org-log-refile :: 'time
> - org-refile-targets :: (("/tmp/b.org" :maxlevel . 1))
> - org-refile-use-outline-path :: 'file
>
> Create an Org buffer named a.org with the following content:
>
> * My pets
> ** Rex
>    Given to me by Theresa.[fn:1]
> * Footnotes
>
> [fn:1] A work colleague.
>
>
> Create an Org file named /tmp/b.org with the following content:
>
> * Her pets
>
> In buffer a.org, with point in Rex, type:
> C-c C-w b.org/Her pets/ <RET>
> M-x org-lint
>
> org-lint complains:
>      4 high  No reference for footnote definition [fn:1]
>
> A similar problem occurs if the entry is archived with org-archive-subtree.  I
> expected Org to automatically detect the footnote inconsistency, without me
> manually invoking org-lint.  Even better would be to fix it, e.g. offer to 
> move
> the footnote definition if there are no other references in the
> current buffer.

Indeed, this is annoying. I do not like much automation, but, in this
case, the problem is difficult to detect, and solve, manually.
Therefore, we should do better.

Besides, we already do something similar when including files in
a document prior to exporting it (we collect included footnotes and make
sure they do not conflict with existing ones in the target document).
So, it may be only a matter of refactoring code.

However, I'd like to keep for after Org 9.0 release.

BTW, would you want to provide a patch?

> Now move to the Footnotes section and refile it to b.org (top level).
> Then on b.org invoke M-x org-lint.  It complains:
>      5 high  Extraneous elements in footnote section
> I expected either org-refile to omit the timestamp when refiling the footnotes
> section (to placate org-lint) or org-lint not to complain about the
> timestamp.

This is a minor issue we shouldn't bother about. Lint just tells you
some parts of the Footnotes section will not be exported. Just ignore
it.

Regards,

-- 
Nicolas Goaziou

Reply via email to