emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [babel] options to the example directive
Date: Wed, 04 Nov 2009 15:01:29 -0700	[thread overview]
Message-ID: <m24opaosp2.fsf@gmail.com> (raw)
In-Reply-To: <87vdhqcebc.fsf@stats.ox.ac.uk> (Dan Davison's message of "Wed, 04 Nov 2009 13:52:55 -0500")

Dan Davison <davison@stats.ox.ac.uk> writes:

> Eric S Fraga <ucecesf@ucl.ac.uk> writes:
>
>> At Tue, 03 Nov 2009 13:57:22 -0700,
>> Eric Schulte wrote:
>>> 
>>> Dan Davison <davison@stats.ox.ac.uk> writes:
>>> 
>>> >
>>> > This is a consequence of the same issue: org-exp-blocks preprocesses
>>> > your src block in a pre-export buffer (a copy of the original), hands it
>>> > to org-babel, which creates the results block (overwriting the version
>>> > where you had manually inserted switches), and that results block lacks
>>> > any switches.
>>> >
>>> 
>>> Would it be worthwhile to add a :results_switches header argument for
>>> passing switches through to a results block?  If that would solve the
>>> problem it should be easy to implement. Best -- Eric
>>
>> Dan & Eric, I think this would be ideal, and results_switches is a
>> perfectly fine name.
>
> That's in branch results-switches at git://repo.or.cz/org-mode/babel.git, with patch below. 
>

This changes has now been merged into the main branch.

      reply	other threads:[~2009-11-04 22:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 14:55 [babel] options to the example directive Eric S Fraga
2009-11-03 17:34 ` Dan Davison
2009-11-03 20:57   ` Eric Schulte
2009-11-04  9:45     ` Eric S Fraga
2009-11-04 18:52       ` Dan Davison
2009-11-04 22:01         ` Eric Schulte [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=m24opaosp2.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=davison@stats.ox.ac.uk \
    --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).