From: "Berry, Charles" via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Jack Kamm <jackkamm@gmail.com>
Cc: Colin Baxter <m43cap@yandex.com>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] ob-R output file with graphics parameter
Date: Sun, 11 Jul 2021 03:23:40 +0000 [thread overview]
Message-ID: <D3807933-AF4E-41C3-87F9-D87BA2470DE4@health.ucsd.edu> (raw)
In-Reply-To: <87fswl7ukj.fsf@gmail.com>
Jack,
I will be going offline for a week or so, so I will have to defer more discussion.
I know that `silent' silences an unwanted file link.
And there are a few other ways to do this.
So, if it is determined to proceed, adding an implicit `file' will not prohibit uses in which it was not actually wanted.
Best,
Chuck
> On Jul 10, 2021, at 2:00 PM, Jack Kamm <jackkamm@gmail.com> wrote:
>
> Hi Chuck,
>
>> If you modify the ECM to change `:exports results' to `:exports
>> none' and clean older fig[12].png's from the directory, the export
>> fails.
>
> Thanks for this example. I had mistakenly thought that code blocks
> with ":exports none" would be evaluated for side effects, but you are
> right, these blocks are skipped altogether during export.
>
> Instead, I think this use case could be handled by the ":results silent"
> header. Blocks with that header are evaluated during export, but the
> result is not inserted into the org buffer or the exported document. It
> seems like a more general way to evaluate code blocks for side effects
> only.
>
> To test this out, you could replace the header arguments in your
> example with:
>
> ":exports results :results graphics file silent :file fig1.png"
>
>> So if everyone else is determined to make this change I can live
>> with it.
>
> I do hope someone submits an RFC, so we can discuss this more
> concretely. I still think it would be nice if we could go back to just
> ":results graphics" to insert a figure. Unfortunately, I'm not currently
> able to propose the patch, as I'm still in limbo w.r.t. my employer
> agreement.
next prev parent reply other threads:[~2021-07-11 3:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 22:50 [PATCH] ob-R output file with graphics parameter Jeremie Juste
2021-06-24 9:21 ` Colin Baxter
2021-06-27 17:12 ` Jack Kamm
2021-06-28 9:56 ` Colin Baxter
2021-06-28 21:54 ` Jeremie Juste
2021-07-03 4:21 ` Jack Kamm
2021-07-03 4:52 ` Timothy
2021-07-03 13:01 ` Jack Kamm
2021-07-03 17:08 ` Jeremie Juste
2021-07-03 18:14 ` Berry, Charles via General discussions about Org-mode.
2021-07-03 20:48 ` Jack Kamm
2021-07-06 15:04 ` Jack Kamm
2021-07-06 17:58 ` Berry, Charles via General discussions about Org-mode.
2021-07-06 19:20 ` Jack Kamm
2021-07-06 21:43 ` Berry, Charles via General discussions about Org-mode.
2021-07-10 10:16 ` Jeremie Juste
2021-07-10 21:00 ` Jack Kamm
2021-07-11 3:23 ` Berry, Charles via General discussions about Org-mode. [this message]
2021-09-26 8:48 ` Bastien
2021-09-26 9:13 ` Jeremie Juste
2021-09-26 9:29 ` Bastien
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=D3807933-AF4E-41C3-87F9-D87BA2470DE4@health.ucsd.edu \
--to=emacs-orgmode@gnu.org \
--cc=ccberry@health.ucsd.edu \
--cc=jackkamm@gmail.com \
--cc=m43cap@yandex.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).