emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: emacs-orgmode@gnu.org
Subject: Manual patch: noweb header argument
Date: Sun, 22 Feb 2015 07:29:05 -1000	[thread overview]
Message-ID: <m2d251kg7y.fsf@tsdye.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 104 bytes --]

Aloha all,

The attached patch recognizes all six possible :noweb header arguments.

All the best,
Tom


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Patch for manual --]
[-- Type: text/x-patch, Size: 960 bytes --]

From 3106e37ba1cfd7fa8e7c1a792a7c69cf76aa5343 Mon Sep 17 00:00:00 2001
From: tsdye <tsd@tsdye.com>
Date: Sun, 22 Feb 2015 07:20:34 -1000
Subject: [PATCH] Revise noweb header argument

---
 doc/org.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 5b4862b..99c6819 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -15618,8 +15618,8 @@ the same session.  Using different session names enables concurrent sessions
 The @code{:noweb} header argument controls expansion of ``noweb'' syntax
 references (see @ref{Noweb reference syntax}) when the code block is
 evaluated, tangled, or exported.  The @code{:noweb} header argument can have
-one of the five values: @code{no}, @code{yes}, @code{tangle}, or
-@code{no-export} @code{strip-export}.
+one of six values: @code{no}, @code{yes}, @code{tangle}, @code{no-export},
+@code{strip-export}, or @code{eval}.
 
 @itemize @bullet
 @item @code{no}
-- 
2.3.0


[-- Attachment #3: Type: text/plain, Size: 146 bytes --]


-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

                 reply	other threads:[~2015-02-22 17:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m2d251kg7y.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).