From: contrapunctus <contrapunctus@disroot.org>
To: emacs-orgmode@gnu.org
Subject: [BUG] org-publish does not obey org-footnote-section [9.6.1 ( @ /home/contrapunctus/.emacs.d/elpa/org-9.6.1/)]
Date: Sat, 04 Feb 2023 10:24:51 +0530 [thread overview]
Message-ID: <871qn6f2sk.fsf@disroot.org> (raw)
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
I have org-footnote-section set to nil in my init.el.
If I export through the HTML or Tufte backends, my footnotes are not exported in a different section. However, with org-publish-project and with org-publish-project-alist having a value like -
(("project" :base-directory "/foo/bar/"
:publishing-directory "/foo/bar/"
:recursive t
:publishing-function org-html-publish-to-tufte-html))
...a section called Footnotes is created.
I have also tried setting org-footnote-section to nil in a .dir-locals.el, in the Org file itself as #+OPTION: org-footnote-section:nil, and as a property in org-publish-project-alist (:org-footnote-section nil)
Emacs : GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.36, cairo version 1.16.0)
of 2023-01-18, modified by Debian
Package: Org mode version 9.6.1 ( @ /home/contrapunctus/.emacs.d/elpa/org-9.6.1/)
next reply other threads:[~2023-02-04 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 4:54 contrapunctus [this message]
2023-02-04 10:51 ` [BUG] org-publish does not obey org-footnote-section [9.6.1 ( @ /home/contrapunctus/.emacs.d/elpa/org-9.6.1/)] Ihor Radchenko
2023-02-04 13:44 ` Ihor Radchenko
[not found] ` <87sffleb2i.fsf@disroot.org>
2023-02-04 15:04 ` Ihor Radchenko
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=871qn6f2sk.fsf@disroot.org \
--to=contrapunctus@disroot.org \
--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).