emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Set exported file name for a headline (LaTeX export)
Date: Tue, 3 Apr 2012 15:25:44 -0500	[thread overview]
Message-ID: <CA+M2ft_36pHFQzDrgcVbD4GbTyvYkw+gnAqTjtj1t1cOEkJ9Pg@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft99mnw2u=kTu9QYyOy8eKJaEVLB-83_BZ7ctcLW6MwHjw@mail.gmail.com>

Sigh.... just had to search harder.
-- http://orgmode.org/manual/Export-options.html


On Tue, Apr 3, 2012 at 3:22 PM, John Hendy <jw.hendy@gmail.com> wrote:
> I create weekly presentations for team meetings at work via
> org-mode/beamer. Currently, these are spread out in a couple of
> directories as separate .org files. It occurred to me that it would be
> fantastic to keep them in one place, as I'm often reusing tables,
> pictures, and whatnot. Is it possible to set a file export name in a
> headline? This could let me keep a file called, say, team-mtgs.org
> where I'd have:
> ----------
> * 2012-04-03
>  :export-file:     ./team-mtg_2012-04-03
>  :END:
> Presentation contents
> * 2012-03-27
>  :export-file:     ./team-mtg_2012-03-27
>  :END:
> Presentation contents
> * 2012-03-20
>  :export-file:     ./team-mtg_2012-03-20
>  :END:
> Presentation contents
> ----------
> I realize this could be goofy, say, if you were exporting all
> headlines (would you export multiple files, combine them all, etc?),
> but I still think it could be really neat. Even the option to split an
> org file into multiple output files is pretty neat. Sorry if this has
> come up before, and thanks for suggestions on how I might accomplish
> this (export sub-headline, rename file, repeat weekly?)
> Thanks,
> John

      reply	other threads:[~2012-04-03 20:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 20:22 Set exported file name for a headline (LaTeX export) John Hendy
2012-04-03 20:25 ` John Hendy [this message]

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=CA+M2ft_36pHFQzDrgcVbD4GbTyvYkw+gnAqTjtj1t1cOEkJ9Pg@mail.gmail.com \
    --to=jw.hendy@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).