[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] externals/org 60f357e8bf: doc/org-manual.org: Clarify that inline
From: |
ELPA Syncer |
Subject: |
[elpa] externals/org 60f357e8bf: doc/org-manual.org: Clarify that inline code blocks cannot be named |
Date: |
Tue, 26 Dec 2023 12:58:17 -0500 (EST) |
branch: externals/org
commit 60f357e8bf704e6c278e7c1fe2dc0fc3ab4558f7
Author: Ihor Radchenko <yantar92@posteo.net>
Commit: Ihor Radchenko <yantar92@posteo.net>
doc/org-manual.org: Clarify that inline code blocks cannot be named
* doc/org-manual.org (Structure of Code Blocks):
---
doc/org-manual.org | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 7db69cbb6e..23f250fa7b 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -17555,7 +17555,8 @@ or
from table formulas (see [[*The Spreadsheet]]) can use the name to
reference a source block. This naming serves the same purpose as
naming Org tables. Org mode requires unique names. For duplicate
- names, Org mode's behavior is undefined.
+ names, Org mode's behavior is undefined. Inline code blocks cannot
+ have a name.
- =#+BEGIN_SRC= ... =#+END_SRC= ::
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [elpa] externals/org 60f357e8bf: doc/org-manual.org: Clarify that inline code blocks cannot be named,
ELPA Syncer <=