emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Tue, 02 Dec 2014 12:23:28 +0100	[thread overview]
Message-ID: <87bnnml2hb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <alpine.LFD.2.11.1411291843240.52834@hafstokkur.hafro.is> (Arni Magnusson's message of "Sat, 29 Nov 2014 18:48:01 +0000 (UTC)")

Arni Magnusson <arnima@hafro.is> writes:

> The location of the second patch (in orgguide.texi) is line 348:

Thanks for the patch.

>> @ vindex org-footnote-section
>> @ noindent Note that the headline @samp{Footnotes} is a @emph{reserved}
>> name. A subtree with this headline will be silently ignored by exporting
>> functions, unless the value of @code{org-footnote-section} is
>>modified.

I think we should emphasize `org-footnote-section' over "Footnotes"
which is but its default value. E.g.,

  Note that a headline named after `org-footnote-section', which defaults
  to @samp{Footnotes}, is considered as special...

Also, Texinfo requires two spaces after a sentence.

Enventually, could you provide the patch with a proper commit message,
using "git format-patch"? You need to add "TINYCHANGE" at the end of the
message if you haven't signed FSF papers yet.


Regards,

  reply	other threads:[~2014-12-02 11:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29 18:48 Warning about section named "Footnotes" Arni Magnusson
2014-12-02 11:23 ` Nicolas Goaziou [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2014-11-28 19:04 Arni Magnusson
2014-11-29 13:31 ` Nicolas Goaziou
2014-11-29 18:40   ` Arni Magnusson

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=87bnnml2hb.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).