emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Aaron Ecay <aaronecay@gmail.com>, 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 07:07:58 -0400	[thread overview]
Message-ID: <87wqeg8fhs.fsf@gmail.com> (raw)
In-Reply-To: 87vbu0d0hs.fsf@bzg.ath.cx

Bastien <bzg@gnu.org> writes:

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

FWIW I'm in full agreement here, see my other email for one sensible
alternative.  (Sorry to split up my reply, the hazards of an
asynch/batch email pull/read/write/push setup.)

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

I agree here.

Thanks again,

>
> Thanks!

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D

  reply	other threads:[~2014-04-23 11:14 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
2014-04-23 11:07       ` Eric Schulte [this message]
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=87wqeg8fhs.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=aaronecay@gmail.com \
    --cc=bzg@gnu.org \
    --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).