Dear Nicolas,

Attached is the formatted patch. I think my email client mangled it last time, as I pasted it inside the email body.

Best regards,

Arni



On Tue, 9 Dec 2014, Nicolas Goaziou wrote:

I have revised the paragraph following your suggestion, and prepared the patch using the 'git format-patch' command. See below.

Thank you. However, I'm unable to apply it. Could you try to update Org first and send it again as an attachment?

Also, you need to specify the node modified in the commit message.


In the past, I have signed FSF papers for Emacs and Texinfo contributions. Does that cover this contribution as well? If not, I'm happy with the TINYCHANGE stamp.

The stamp is not needed, then.
From 72bda40525eed23941046694382814e3d04d9b97 Mon Sep 17 00:00:00 2001
From: Arni Magnusson <arn...@hafro.is>
Date: Sat, 21 Feb 2015 16:08:43 +0000
Subject: [PATCH] Add documentation regarding reserved keywords in @node
 Headlines

---
 doc/org.texi      | 8 +++++++-
 doc/orgguide.texi | 6 +++++-
 2 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index bec46a9..8c7e3c3 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -1208,7 +1208,13 @@ headings indented less than 30 stars.}.  For example:
 * Another top level headline
 @end example
 
-@noindent Some people find the many stars too noisy and would prefer an
+@vindex org-footnote-section
+@noindent Note that a headline named after @code{org-footnote-section},
+which defaults to @samp{Footnotes}, is considered as special.  A subtree
+with this headline will be silently ignored by exporting functions,
+unless the value of @code{org-footnote-section} is modified.
+
+Some people find the many stars too noisy and would prefer an
 outline that has whitespace followed by a single star as headline
 starters.  @ref{Clean view}, describes a setup to realize this.
 
diff --git a/doc/orgguide.texi b/doc/orgguide.texi
index e32fa7c..7308d32 100644
--- a/doc/orgguide.texi
+++ b/doc/orgguide.texi
@@ -345,7 +345,11 @@ of @kbd{C-a} and @kbd{C-e} in headlines.}.  For example:
 * Another top level headline
 @end smallexample
 
-@noindent 
+@noindent Note that a headline named after @code{org-footnote-section},
+which defaults to @samp{Footnotes}, is considered as special.  A subtree
+with this headline will be silently ignored by exporting functions,
+unless the value of @code{org-footnote-section} is modified.
+
 Some people find the many stars too noisy and would prefer an
 outline that has whitespace followed by a single star as headline
 starters.  @ref{Clean view}, describes a setup to realize this.
-- 
1.8.3.1

Reply via email to