emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: unnamed :results
Date: Wed, 05 Jan 2011 09:20:11 -0700	[thread overview]
Message-ID: <87mxnfmhgd.fsf@gmail.com> (raw)
In-Reply-To: 81CF2144-4011-4ED7-AD46-3BA6A590A70B@tsdye.com

Hmm,

I think the code has always named results blocks after the code block
when the code block has a name.  I would expect your "new" behavior
below to have been the standard behavior since the early days of babel.

Best -- Eric

"Thomas S. Dye" <tsd@tsdye.com> writes:

> Aloha all,
>
> In the course of updating an Org-mode file to take account of the new  
> file output handling for R, I noticed a change in the naming of  
> results blocks.  In the example below, the top #+results: line was  
> produced with the most recent Org-mode from git.  The previous  
> behavior is on the following line.
>
> #+srcname: r-complete-length-histogram-pdf
> #+begin_src R :results output graphics :file r/adze_len_eg.png :var  
> x=whole-adzes
>   library(ggplot2)
>   adze.len <- ggplot(x, aes(length_poll))
>   adze.len + geom_histogram()
> #+end_src
>
>
> #+results:
> [[file:r/adze_len_eg.png]]
>
> #+results: r-complete-length-histogram-pdf
> [[file:r/adze_len_eg.png]]
>
> The only change (other than updating Org-mode) was the addition of  
> graphics to the :results header argument.
>
> All the best,
> Tom
>
> _______________________________________________
> 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-05 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-01 23:34 unnamed :results Thomas S. Dye
2011-01-05 16:20 ` Eric Schulte [this message]
2011-01-05 18:23   ` Thomas S. Dye

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=87mxnfmhgd.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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
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).