From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Arni Magnusson <arnima@hafro.is>
Cc: emacs-orgmode@gnu.org
Subject: Re: Warning about section named "Footnotes"
Date: Sat, 29 Nov 2014 14:31:13 +0100 [thread overview]
Message-ID: <87a93annfi.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <alpine.LFD.2.11.1411281850310.35131@hafstokkur.hafro.is> (Arni Magnusson's message of "Fri, 28 Nov 2014 19:04:40 +0000 (GMT)")
Hello,
Arni Magnusson <arnima@hafro.is> writes:
> I was using Org to write a software manual with a structure along the
> lines of:
>
>
> * Equations
>
> How to write equations in software FOO.
>
> * Footnotes
>
> How to write footnotes in software FOO.
>
> * Images
>
> How to insert images in software FOO.
>
>
> When I exported the document (to LaTeX and HTML), I was puzzled to
> find that one of the sections was not exported at all...
>
> After investigating the problem for a while, I realized that if
> a section is named "Footnotes" the default behavior of Org is to
> ignore it silently.
>
> My solution was to set `org-footnote-section' to nil.
>
>
> I think it would help Org users if:
>
> 1. Org export (to LaTeX, HTML, etc.) emits an error or a prominent warning
> when it ignores an entire section like this.
It shouldn't. This is the expected behaviour.
> 2. The manual would warn the user about this behavior with a prominent
> warning.
Would you mind suggesting a change to the manual?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-11-29 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 19:04 Warning about section named "Footnotes" Arni Magnusson
2014-11-29 13:31 ` Nicolas Goaziou [this message]
2014-11-29 18:40 ` Arni Magnusson
-- strict thread matches above, loose matches on Subject: below --
2014-11-29 18:48 Arni Magnusson
2014-12-02 11:23 ` Nicolas Goaziou
2014-12-08 1:37 ` Arni Magnusson
2014-12-09 8:56 ` Nicolas Goaziou
2015-02-21 16:36 ` Arni Magnusson
2015-02-21 17:33 ` 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=87a93annfi.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=arnima@hafro.is \
--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).