emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Documentation patch
Date: Sat, 1 Jan 2011 10:21:40 -1000	[thread overview]
Message-ID: <C9BC9C2A-55E4-4F86-9483-290749F85497@tsdye.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 218 bytes --]

Aloha all,

The attached patch documents multi-line headers for source code blocks:



Thomas S. Dye, Ph.D.
T. S. Dye & Colleagues, Archaeologists, Inc.
Phone: (808) 529-0866 Fax: (808) 529-0884
http://www.tsdye.com



[-- Attachment #1.2.1: Type: text/html, Size: 256 bytes --]

[-- Attachment #1.2.2: babel-multi-line-header.patch --]
[-- Type: application/octet-stream, Size: 1170 bytes --]

Changes in HEAD
	Modified doc/org.texi
diff --git a/doc/org.texi b/doc/org.texi
index f324d04..efa892e 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -11601,6 +11601,33 @@ Similarly, it is possible to set header arguments for inline code blocks:
 src_haskell[:exports both]@{fac 5@}
 @end example
 
+Code block header arguments can span multiple lines using =#+header:= or
+=#+headers:= lines preceding a code block or nested in between the name and
+body of a named code block.
+
+Multi-line header arguments on an un-named code block:
+@example
+ #+headers: :var data1=1
+ #+begin_src emacs-lisp :var data2=2
+   (message "data1:%S, data2:%S" data1 data2)
+ #+end_src
+
+ #+results:
+ : data1:1, data2:2
+@end example
+
+Multi-line header arguments on a named code block:
+@example
+   #+source: named-block
+   #+header: :var data=2
+   #+begin_src emacs-lisp
+     (message "data:%S" data)
+   #+end_src
+
+   #+results: named-block
+   : data:2
+@end example
+
 @node Header arguments in function calls,  , Code block specific header arguments, Using header arguments
 @comment  node-name,  next,  previous,  up
 @subsubheading Header arguments in function calls


[-- Attachment #1.2.3: Type: text/html, Size: 2109 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

             reply	other threads:[~2011-01-01 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-01 20:21 Thomas S. Dye [this message]
2011-01-05 16:10 ` Documentation patch Eric Schulte
  -- strict thread matches above, loose matches on Subject: below --
2016-01-06 17:28 Thomas S. Dye
2016-01-06 21:58 ` Nicolas Goaziou
2015-07-27  0:44 Thomas S. Dye
2015-07-27  8:21 ` Rasmus
2006-05-24  9:57 Christian Egli
2006-05-24 10:04 ` Carsten Dominik

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=C9BC9C2A-55E4-4F86-9483-290749F85497@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).