emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Aaron Ecay <aaronecay@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Date: Tue, 22 Apr 2014 23:22:04 +0200	[thread overview]
Message-ID: <87bnvt2h6r.fsf@bzg.ath.cx> (raw)
In-Reply-To: <1398196476-4773-1-git-send-email-aaronecay@gmail.com> (Aaron Ecay's message of "Tue, 22 Apr 2014 15:54:36 -0400")

Hi Aaron,

thanks for the patch.

Aaron Ecay <aaronecay@gmail.com> writes:

> #+name: one
> #+begin_src R :results file graphics :file png
>   ...
> #+end_src

What happens when there is :file png with no #+name line?

> The benefit comes from the reduced duplication of information in the
> file.  It also becomes possible to use the usual property inheritance
> mechanisms (via #+PROPERTY lines or :PROPERTY: drawers) to specify
> result file types for multiple source blocks at once.
> This patch also introduces the :output-dir property, which can be used
> to redirect all the output from blocks in a (file/subtree) to a
> subdirectory.

Does :output-dir accept absolute or relative paths?  I'm asking
because you speak of "subdirectory", but both should be accepted

> The patch treats any :file args containing a period as before, so
> backwards compatibility with old files should in most cases be
> maintained.

Maybe there are cases where the :file value does not take an extension
but the user still want to write the output to this file?  How would
your patch handle this?

> If this patch looks good, I can provide tests and documentation.

Looks useful to me, but ":file png" looks wrong, with too much
implicit.  We should find something less confusing.



  reply	other threads:[~2014-04-22 21:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 19:54 [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks Aaron Ecay
2014-04-22 21:22 ` Bastien [this message]
2014-04-23  0:04   ` Aaron Ecay
2014-04-23  1:35     ` Eric Schulte
2014-04-23 14:58       ` Bastien
2014-04-28  2:18       ` Aaron Ecay
2014-04-28  6:20         ` Achim Gratz
2014-04-29 13:25         ` Bastien
2014-05-04 13:55         ` Eric Schulte
2014-05-11 20:38           ` Aaron Ecay
2014-05-14 17:46             ` Achim Gratz
2014-05-15 10:05               ` Bastien
2014-05-16  3:28               ` Aaron Ecay
2014-05-17  6:20                 ` Achim Gratz
2014-04-23  6:27     ` Bastien
2014-04-23 11:07       ` Eric Schulte
2014-04-23 19:44     ` Achim Gratz

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:

  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=87bnvt2h6r.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).