From: tsd@tsdye.com (Thomas S. Dye)
To: Org-mode <emacs-orgmode@gnu.org>
Subject: [PATCH] Documentation of :results wrap
Date: Sat, 07 Jan 2012 20:42:20 -1000 [thread overview]
Message-ID: <m1fwfqu243.fsf@tsdye.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 123 bytes --]
Aloha all,
The attached patch to the Org mode manual describes the current behavior
of :results wrap.
All the best,
Tom
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Manual patch --]
[-- Type: text/x-patch, Size: 1066 bytes --]
From bc7b5fe2cc52de4468cf847e72cb0a507ebb1626 Mon Sep 17 00:00:00 2001
From: Thomas Dye <dk@poto.local>
Date: Sat, 7 Jan 2012 20:38:53 -1000
Subject: [PATCH] * doc/org.texi: :results wrap produces a drawer instead of a
begin_results block
---
doc/org.texi | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index bc82e0b..c4031d7 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -13351,9 +13351,9 @@ The result is converted to pretty-printed code and is enclosed in a code
block. This option currently supports Emacs Lisp, Python, and Ruby. E.g.,
@code{:results value pp}.
@item @code{wrap}
-The result is wrapped in a @code{begin_result} block. This can be useful for
+The result is wrapped in a RESULTS drawer. This can be useful for
inserting @code{raw} or @code{org} syntax results in such a way that their
-extend is known and they can be automatically removed or replaced.
+extent is known and they can be automatically removed or replaced.
@end itemize
@subsubheading Handling
--
1.7.5.4
[-- 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
next reply other threads:[~2012-01-08 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 6:42 Thomas S. Dye [this message]
2012-01-08 16:17 ` [PATCH] Documentation of :results wrap 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=m1fwfqu243.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).