emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ian Barton <lists@wilkesley.net>
To: Dieter Van Eessen <dieter.van.eessen@gmail.com>,
	org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Setting The Output Directory for Markdown Export.
Date: Mon, 19 Jan 2015 11:38:59 +0000	[thread overview]
Message-ID: <54BCECD3.2040106@wilkesley.net> (raw)
In-Reply-To: <CAC2TPPg_0NSssePL5v-8fCYn4edQcMto0b6Top0MvrVuANGn_w@mail.gmail.com>

Thanks, that's a good idea. However, half an hour after posting my 
message I discovered #+EXPORT_FILENAME, which does exactly what  want!


On 19/01/15 11:06, Dieter Van Eessen wrote:
> Hello,
> Just something which might be usefull as a workaround.
> I know org-babel-tangle allows you to tangle blocks to certain location,
> and there is also a hook available for post-processing.
> Now what if you'd put your whole file in a source block, with language
> 'org',
> tangle it to the location you want and use exporting capabilities as
> post-processing tool?
> Could be an awfull workaround :)
> but it's the first thing that popped up in my mind when reading your
> question
> have fun,
> Dieter
> On Mon, Jan 19, 2015 at 11:53 AM, Ian Barton <lists@wilkesley.net
> <mailto:lists@wilkesley.net>> wrote:
>     I want to export a single file to somewhere other than its current
>     directory. Using publish seems to be over the top for this simple
>     use case.
>     I can't find a variable or in buffer option that lets me set the
>     output directory. Searching the list turns up
>     org-export-publishing-__directory, but this seems to have been
>     deprecated. Is there something obvious I have missed?
>     Ian.

  reply	other threads:[~2015-01-19 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 11:06 Setting The Output Directory for Markdown Export Dieter Van Eessen
2015-01-19 11:38 ` Ian Barton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-19 10:53 Ian Barton

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=54BCECD3.2040106@wilkesley.net \
    --to=lists@wilkesley.net \
    --cc=dieter.van.eessen@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ian@manor-farm.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).