From: Christophe Pouzat <christophe.pouzat@gmail.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Question related to org-babel-expand-src-block
Date: Fri, 03 Feb 2012 21:20:54 +0100 [thread overview]
Message-ID: <87y5sjwtw9.fsf@xtof-netbook.home> (raw)
In-Reply-To: <87bopfsqf7.fsf@gmx.com> (Eric Schulte's message of "Fri, 03 Feb 2012 11:49:32 -0700")
Eric Schulte <eric.schulte@gmx.com> writes:
> Christophe Pouzat <christophe.pouzat@gmail.com> writes:
>
>> Hi all,
>>
>> Using the last org-mode version from the git repository (7.8.03) I've found a
>> mismatch between the key-chord required to call function
>> =org-babel-expand-src-block= (=C-c C-v v=) and the ones given in the
>> info file: =C-c C-v p= or =C-c C-v C-p=. The same goes for the
>> [[http://orgmode.org/worg/org-contrib/babel/intro.html][Babel:
>> Introduction]] where the given key-chord is =C-c M-b p=.
>>
>> In the same line, I have a question concerning the inclusion of the
>> /expanded/ source block in the generated output. Let's assume that I
>> define in my =.org= file a variable containing a file name like:
>>
>> #+name: my-file-name
>> : dataFile.mat
>>
>> I want then a code block (using =R= in that case) that checks if
>> "dataFile.mat" is in the working directory with something like:
>>
>> #+BEGIN_SRC R :var fileName=my-file-name :exports both
>> fileName %in% list.files(pattern="*.mat")
>> #+END_SRC
>>
>> I'm passing the file name as a variable because I want to repeat the same
>> analysis on different data files. But I would like to see in the HTML output
>> the value of the above variable =fileName=. I would like essentially to
>> export the expanded source block. Is there a way to do that?
>>
>> Thanks,
>>
>> Christophe
>
> Hi Christophe,
>
> Thanks for reporting the documentation issue, I've just pushed up a
> patch which updates the documentation appropriately.
>
> I do not believe there is a way to export an expanded code blocks, and I
> fear you may not want to see the variable assignment code in your
> export. You can however use noweb references to achieve the behavior
> you are after with the following.
>
> #+name: my-file-name
> : dataFile.mat
>
> #+BEGIN_SRC R :exports both :noweb yes
> <<my-file-name()>> %in% list.files(pattern="*.mat")
> #+END_SRC
>
> Best,
Hi Eric,
I agree with you: I don't want to see the variable assignment code in my
export in general – in particular if this means assigning a big matrix to
a variable.
I will try your noweb suggestion for the few cases where I want to
export the assignment.
Thanks for your help.
Christophe
--
Most people are not natural-born statisticians. Left to our own
devices we are not very good at picking out patterns from a sea of
noisy data. To put it another way, we are all too good at picking out
non-existent patterns that happen to suit our purposes.
Bradley Efron & Robert Tibshirani (1993) An Introduction to the Bootstrap
--
Christophe Pouzat
MAP5 - Mathématiques Appliquées à Paris 5
CNRS UMR 8145
45, rue des Saints-Pères
75006 PARIS
France
tel: +33142863828
mobile: +33662941034
web: http://www.biomedicale.univ-paris5.fr/physcerv/C_Pouzat.html
prev parent reply other threads:[~2012-02-03 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 17:52 Question related to org-babel-expand-src-block Christophe Pouzat
2012-02-03 18:49 ` Eric Schulte
2012-02-03 20:20 ` Christophe Pouzat [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=87y5sjwtw9.fsf@xtof-netbook.home \
--to=christophe.pouzat@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.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).