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: Wed, 23 Apr 2014 08:27:11 +0200 [thread overview]
Message-ID: <87vbu0d0hs.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87d2g92au5.fsf@gmail.com> (Aaron Ecay's message of "Tue, 22 Apr 2014 20:04:43 -0400")
Hi Aaron,
Aaron Ecay <aaronecay@gmail.com> writes:
> How does this sound as an algorithm:
> 1. if :file is present, behave exactly as we do now
> 2. if :file is absent but :file-ext and a #+name is present, generate a
> :file parameter from :output-dir, the #+name, and :file-ext.
I suggest this one:
1. if :file is present, behave exactly as we do now
2. if :file-ext is present:
- if #+name is present, generate a :file parameter
from :output-dir, #+name and :file-ext
- otherwise, generate the :file parameter from
:output-dir, the headline or the title or the
current file name and :file-ext
Just falling back on something sensible when :file is absent
and :file-ext is specified.
> Open questions:
> 1. should :file-ext without a #+name be a no-op, or an error?
See above.
> 2. should :output-dir apply to the :file case as well?
To me yes.
In overall I think would be good, but I'd like Eric and other
babelist around here to have a look before we commit this.
So perhaps another round of patch testing will be good.
Thanks!
--
Bastien
next prev parent reply other threads:[~2014-04-23 6:27 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
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 [this message]
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:
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=87vbu0d0hs.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=aaronecay@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).