emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: contrapunctus <contrapunctus@disroot.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [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 13:44:45 +0000	[thread overview]
Message-ID: <87cz6pfstu.fsf@localhost> (raw)
In-Reply-To: <871qn6f2sk.fsf@disroot.org>

contrapunctus <contrapunctus@disroot.org> writes:

> 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.

Please provide more details about how to reproduce the issue.
May you attach a small example file and details steps demonstrating the
issue? See https://orgmode.org/manual/Feedback.html#Feedback

> ... #+OPTION: org-footnote-section:nil, and as a property in
> org-publish-project-alist (:org-footnote-section nil)

These two options will have no effect. org-footnote-section cannot be
set using OPTIONS and project alist. Just variable.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  parent reply	other threads:[~2023-02-04 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04  4:54 [BUG] org-publish does not obey org-footnote-section [9.6.1 ( @ /home/contrapunctus/.emacs.d/elpa/org-9.6.1/)] contrapunctus
2023-02-04 10:51 ` Ihor Radchenko
2023-02-04 13:44 ` Ihor Radchenko [this message]
     [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=87cz6pfstu.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=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).