branch: externals/org
commit dca67295968af8ce297c3ddc0a95ce5a61b9fa76
Author: Rudolf Adamkovič <[email protected]>
Commit: Ihor Radchenko <[email protected]>
doc/org-manual: Clarify COMMENT behavior with respect to tangling
* doc/org-manual.org (Comment Lines): Explain how COMMENT suppresses
not only source block execution but also tangling.
---
doc/org-manual.org | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 158623d361..d529ab5f64 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -12948,9 +12948,9 @@ leading =*= with =,= to avoid interpreting them as
headings.]
Finally, a =COMMENT= keyword at the beginning of an entry, but after
any other keyword or priority cookie, comments out the entire subtree.
In this case, the subtree is not exported and no code block within it
-is executed either[fn:: For a less drastic behavior, consider using a
-select tag (see [[*Export Settings]]) instead.]. The command below
-helps to change the comment status of a headline.
+is executed or tangled[fn:: For less restrictive export limitations,
+consider using a select tag (see [[*Export Settings]]) instead.]. The
+command below helps to change the comment status of a headline.
- {{{kbd(C-c ;)}}} (~org-toggle-comment~) ::
#+kindex: C-c ;
