From: Dan Davison <dandavison7@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: return link to :file when using #+call
Date: Sun, 23 Jan 2011 09:14:39 +0000 [thread overview]
Message-ID: <m162tgnfr4.fsf@gmail.com> (raw)
In-Reply-To: 20110123011309.69b6a11c@bill
Myles English <mylesenglish@gmail.com> writes:
> Thanks for your answer Eric. Recent changes as per
> http://thread.gmane.org/gmane.emacs.orgmode/35396
> means that this no longer works.
Thanks for bringing this up Myles.
> To recap: what I would like to do is to #+call an R source
> block, passing a filename, and have it write a plot to that file and
> also insert a link to that file in the org file. Any ideas?
>
> Here is what I have tried:
>
> #+source: foo()
> #+begin_src R :file bar.png :results graphics
> plot(1,1)
> #+end_src
>
>
> #+call: foo[:file baz.png]()
>
> #+results: foo[:file baz.png]()
> : baz.png
>
> baz.png contains a plot, but no file link is inserted.
Yes you need :results file, so the line should be
#+call: foo[:file baz.png]() :results file
Explanation: In simple single-block usage, :file automatically
sets :results file. But here :file in square brackets is passed to block
foo, so the #+call line needs its own :results file. (And in fact :file
would be wrong; see below).
>
> #+call: foo()
>
> #+results: foo()
> : bar.png
>
> bar.png contains a plot, but no file link is inserted.
Yep. Same as above, except here you haven't overridden the file name.
> #+call: foo[:file biff.png]() :file biff.png
>
> #+results: foo[:file biff.png]()
> [[file:biff.png]]
>
> a file link is inserted but file biff.png contains 'biff.png'
Right, this one's kind of instructive for understanding this
stuff. Here, foo returns its file name as a string, so
"biff.png". The #+call line has been told to send its results to file
with the :file argument, and it takes that literally, writing the string
"biff.png" to its output file. So if what we want is a file containing
graphics, we are not going to want :file on the #+call line. What we
want is to interpret the string as a file name, and that's what :results
file does.
>
> #+call: foo[:file pow.png]() :file pow.png :results graphics
>
> #+results: foo[:file pow.png]()
> [[file:pow.png]]
>
> a file link is inserted but file pow.png contains 'pow.png'
Same as above. #+call receives a string from foo; it can't turn that
string into the desired graphics. In fact, :results graphics currently
only has any effect on an R block (i.e. at an R block, or passed to an R
block inside [ ... ]).
Dan
>
> Thanks,
>
> Myles
>
>
> On Wed, 05 Jan 2011 23:28:00 -0700
> "Eric Schulte" <schulte.eric@gmail.com> wrote:
>
>> Hi Myles,
>>
>> Currently I believe the best option is the solution you posted below,
>> the file name is repeated because both the code block and the call
>> line need to know the file name to create the file and the link
>> respectively.
>>
>> Cheers -- Eric
>>
>> Myles English <mylesenglish@gmail.com> writes:
>>
>> > Myles English <mylesenglish <at> gmail.com> writes:
>> >
>> >> #+source: foo()
>> >> #+begin_src R :file bar.png
>> >> plot(1,1)
>> >> #+end_src
>> >
>> > This works but I have to repeat the filename:
>> >
>> > #+call: foo[:file baz.png]() :file baz.png
>> >
>> > #+results: foo[:file baz.png]()
>> > [[file:baz.png]]
>> >
>> > Myles
>> >
>> >
>> > _______________________________________________
>> > 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
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2011-01-23 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 0:05 return link to :file when using #+call Myles English
2011-01-01 22:57 ` Myles English
2011-01-06 6:28 ` Eric Schulte
2011-01-23 1:13 ` Myles English
2011-01-23 9:14 ` Dan Davison [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=m162tgnfr4.fsf@gmail.com \
--to=dandavison7@gmail.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).