branch: externals/org
commit 9e62aaf5e47eb8356a86da5120c15231fad45cc4
Author: Ihor Radchenko <yanta...@posteo.net>
Commit: Ihor Radchenko <yanta...@posteo.net>
doc/org-manual.org: Suggest keywords to have space after colon
* doc/org-manual.org (Summary of In-Buffer Settings): Declare that
keywords have space after colon. This is not strictly true with the
current parser, but it will avoid problems when no space is given and
the value contains ":" in it.
Reported-by: Olivier <olivier...@gmail.com>
Link:
https://orgmode.org/list/caefuq3hwmvq-ajg51sm1pmy3y1vferarxcs5j3zxhudcn9j...@mail.gmail.com
---
doc/org-manual.org | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 1369ab0bd6..d0cde3e156 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -19777,9 +19777,10 @@ manual, but here is a consolidated list for easy
reference.
#+cindex: special keywords
In-buffer settings start with =#+=, followed by a keyword, a colon,
-and then a word for each setting. Org accepts multiple settings on
-the same line. Org also accepts multiple lines for a keyword. This
-manual describes these settings throughout. A summary follows here.
+one or more spaces, and then a word for each setting. Org accepts
+multiple settings on the same line. Org also accepts multiple lines
+for a keyword. This manual describes these settings throughout. A
+summary follows here.
#+cindex: refresh set-up
{{{kbd(C-c C-c)}}} activates any changes to the in-buffer settings.
