emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Thomas S. Dye" <tsd@tsdye.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [Babel] [Ann] varied updates and improvements
Date: Sat, 1 Jan 2011 11:01:04 -1000	[thread overview]
Message-ID: <5DE633CA-0B3B-4EDB-B38E-F0DFCBE57418@tsdye.com> (raw)
In-Reply-To: <87lj5r1vf8.fsf@gmail.com>

Aloha all,

I'm seeing some unexpected behavior with source blocks as I'm  
adding :cache yes as a multi-line header argument.  The top #+results:  
is with the addition of the #+header: :cache yes line.  Note the lack  
of a :results name and also the lack of the SHA1 hash.  The bottom # 
+results: line is the result before addition of the #+header: line.

#+srcname: r-edge-angle-histogram
#+header: :cache yes
#+begin_src R :results output :var x=whole-adzes :file r/ 
adze_edge_angle.png :width 400 :height 300
   library(ggplot2)
   adze.edge.angle <- ggplot(x, aes(edge_angle))
   adze.edge.angle + geom_histogram(aes(y=..density..)) +
   geom_density(weight=2) + xlab("Measured cutting edge angle  
(degrees)")
#+end_src

#+results:
[[file:r/adze_edge_angle.png]]

#+results: r-edge-angle-histogram
[[file:r/adze_edge_angle.png]]


All the best,
Tom

On Oct 21, 2010, at 4:18 AM, Eric Schulte wrote:

> Multi-line header arguments to code blocks
> -------------------------------------------
> Code block header arguments can now span multiple lines using the
> new =#+header:= or =#+headers:= lines preceding a code block or
> nested in between the name and body of a named code block.
> Examples are given below.
>
> - multi-line header arguments on an un-named code block
>  #+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
>
> - multi-line header arguments on a named code block
>    #+source: named-block
>    #+header: :var data=2
>    #+begin_src emacs-lisp
>      (message "data:%S" data)
>    #+end_src
>
>    #+results: named-block
>    : data:2

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 14:18 [Babel] [Ann] varied updates and improvements Eric Schulte
2011-01-01 20:41 ` Thomas S. Dye
2011-01-01 21:09   ` Thomas S. Dye
2011-01-01 21:01 ` Thomas S. Dye [this message]

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=5DE633CA-0B3B-4EDB-B38E-F0DFCBE57418@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    /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

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