From: tsd@tsdye.com (Thomas S. Dye)
To: Org-mode <emacs-orgmode@gnu.org>
Subject: [PATCH] Revise manual entry for :noweb no
Date: Tue, 10 Jan 2012 06:10:44 -1000 [thread overview]
Message-ID: <m139bna67v.fsf@tsdye.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 139 bytes --]
Aloha all,
The attached patch to the manual is intended to make the description of
:noweb no conform to its behavior.
All the best,
Tom
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Patch for noweb no --]
[-- Type: text/x-patch, Size: 1122 bytes --]
From 7207cdec84daecd31d4e53117c477abaad91bbd1 Mon Sep 17 00:00:00 2001
From: Thomas Dye <dk@poto.local>
Date: Tue, 10 Jan 2012 06:06:49 -1000
Subject: [PATCH] * doc/org.texi: Edit :noweb no header argument for
correctness
---
doc/org.texi | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index c4031d7..c3405f1 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -13583,9 +13583,8 @@ argument can have one of three values: @code{yes}, @code{no}, or @code{tangle}.
All ``noweb'' syntax references in the body of the code block will be
expanded before the block is evaluated, tangled or exported.
@item @code{no}
-The default. No ``noweb'' syntax specific action is taken on evaluating
-code blocks, However, noweb references will still be expanded during
-tangling.
+The default. No ``noweb'' syntax specific action is taken when the code
+block is evaluated, tangled or exported.
@item @code{tangle}
All ``noweb'' syntax references in the body of the code block will be
expanded before the block is tangled, however ``noweb'' references will not
--
1.7.5.4
[-- Attachment #3: Type: text/plain, Size: 40 bytes --]
--
Thomas S. Dye
http://www.tsdye.com
next reply other threads:[~2012-01-10 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 16:10 Thomas S. Dye [this message]
2012-01-10 16:46 ` [PATCH] Revise manual entry for :noweb no Eric Schulte
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=m139bna67v.fsf@tsdye.com \
--to=tsd@tsdye.com \
--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).