From: Jack Kamm <jackkamm@gmail.com>
To: Tyler Smith <tyler@plantarum.ca>,
Emacs Org-Mode Help <emacs-orgmode@gnu.org>
Subject: Re: Bug: R src blocks fail to produce link to graphics file [9.3 org-plus-contrib-20200127]
Date: Mon, 27 Jan 2020 17:13:35 -0800 [thread overview]
Message-ID: <87ftg0e62o.fsf@gmail.com> (raw)
In-Reply-To: <38d7ec9f-7e36-4b82-b1cf-03701b66eb1f@www.fastmail.com>
> Is the rationale explained anywhere? After a bit of poking around, it looks like using the `:file` flag without a `file` argument to results doesn't do anything (no file is created), nor does the reverse. That is, unless you use both the `file` argument and the `:file` option, nothing happens. Is there a situation where you can use `:file` to do something that doesn't require a `file` argument to `:results`?
The specific commit where it happened was
26ed66b23335eb389f1f2859e409f46f66279e15, which says:
"Deducing the results from some other arguments is not obvious.
Moreover, it prevents users from setting, e.g., :file-ext, in a node
property, as every block would then create a file."
The commit also links to this thread:
http://lists.gnu.org/r/emacs-orgmode/2018-05/msg00469.html
I wasn't involved in that discussion, but I think the idea is that you
could create a subtree with many named source blocks each creating a PNG
file, set the :file-ext parameter at the subtree level, and have the
file names auto-created from the source block names.
> The documentation for ob-R is now incorrect:
>
> https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html
Yes, also that page could use some other updates, e.g. there are some
dead links in there.
next prev parent reply other threads:[~2020-01-28 1:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 16:13 Bug: R src blocks fail to produce link to graphics file [9.3 org-plus-contrib-20200127] Tyler Smith
2020-01-27 16:27 ` Jeremie
2020-01-27 16:58 ` Tyler Smith
2020-01-27 17:22 ` William Denton
2020-01-27 17:29 ` Jack Kamm
2020-01-27 17:52 ` Tyler Smith
2020-01-28 1:13 ` Jack Kamm [this message]
2020-02-17 17:40 ` Jack Kamm
2020-02-18 14:58 ` Tyler Smith
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=87ftg0e62o.fsf@gmail.com \
--to=jackkamm@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tyler@plantarum.ca \
/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).