From: Myles English <mylesenglish@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: return link to :file when using #+call
Date: Sat, 1 Jan 2011 22:57:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20110101T235059-402@post.gmane.org> (raw)
In-Reply-To: 20101231000534.3e9e97ea@bill
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
next prev parent reply other threads:[~2011-01-01 23:00 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 [this message]
2011-01-06 6:28 ` Eric Schulte
2011-01-23 1:13 ` Myles English
2011-01-23 9:14 ` Dan Davison
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=loom.20110101T235059-402@post.gmane.org \
--to=mylesenglish@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).