From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Ista Zahn <istazahn@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>,
Alan L Tyree <alantyree@gmail.com>
Subject: Re: Export each top level heading to separate file
Date: Sun, 5 Jan 2014 08:40:46 -0500 [thread overview]
Message-ID: <CAJ51ETqfUdr9=qCC3QSLhMNsVszhie7eOO_JogS-B-mknPT1mw@mail.gmail.com> (raw)
In-Reply-To: <CA+vqiLENf-FMJ8OLK6awAJx8Y_EdsjKPQ=EisVahm+zUE=DfwQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3406 bytes --]
Try this:
(org-map-entries
(lambda ()
(let ((level (nth 1 (org-heading-components)))
(title (nth 4 (org-heading-components))))
(if (= level 1)
(org-entry-put (point) ":EXPORT_FILE_NAME:" title))))
nil nil)
It seems to do what you want.
John
-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Sat, Jan 4, 2014 at 7:36 PM, Ista Zahn <istazahn@gmail.com> wrote:
> On Sat, Jan 4, 2014 at 6:41 PM, Alan L Tyree <alantyree@gmail.com> wrote:
> > On 05/01/14 09:45, Charles Millar wrote:
> >>
> >> Ista and all,
> >>
> >> On 1/4/2014 5:29 PM, Ista Zahn wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I'm looking for a way to export each top-level heading to a separate
> >>> markdown file. Ideally I would like to have the exported files named
> >>> according to the heading. For example I would like this org file
> >>>
> >>> -----------------------------------
> >>> * Section one
> >>> Section one text
> >>> * Section two
> >>> ** Section two a
> >>> Section two text
> >>> * Section three
> >>> Section three text
> >>> -----------------------------------
> >>>
> >>> To generate three files:
> >>>
> >>> --- Section one.md ---
> >>> Section one text
> >>>
> >>> -----------------------------------
> >>>
> >>> --- Section two.md---
> >>> ## Section two a
> >>>
> >>> Section two text
> >>>
> >>> -----------------------------------
> >>>
> >>> --- Section three.md -
> >>> # Section three
> >>>
> >>> Section three text
> >>>
> >>> -----------------------------------
> >>>
> >>> I suspect that the publishing framework might support this, but I've
> >>> thus far avoided it because it looks pretty complicated to set up.
> >>> Before I dive in I'd like to know if the publishing framework is the
> >>> correct place to look for this functionality or if there is an easier
> >>> way to do it.
> >>>
> >>>
> >>
> >> I have a similar question regarding LaTeX export. How to export a
> heading
> >> (any heading, regardless of level) within a file to heading.tex instead
> of
> >> file.tex? So far the only solution I have cobbled together is to C-x C-f
> >> 'file.tex" and then C-x C-w "heading.tex" . I then typeset heading.tex
> >> using TeXworks. Perhaps I should note that my exported heading is
> tagged so
> >> that the heading is ignored.
> >>
> >> Charlie Millar
> >>
> >> ---
> >> This email is free from viruses and malware because avast! Antivirus
> >> protection is active.
> >> http://www.avast.com
> >>
> >>
> >>
> > Use properties to set the export file name -- example:
> > :PROPERTIES:
> > :EXPORT_TITLE: Internet banking fraud
> > :EXPORT_FILE_NAME: internet-fraud
> > :EXPORT_AUTHOR: Alan L Tyree
> > :Citation: (2011) 22 JBFLP 214
> > :EXPORT_OPTIONS: num:nil toc:nil
> > :END:
>
> Thanks, gets me half the way there. Setting properties as you
> described and exporting each sub-tree works properly. Now how can I do
> this for all the top-level headings in a file?
>
> Best,
> Ista
>
> >
> > If I understood your question properly.
> >
> > Cheers,
> > Alan
> >
> >
> >
> > --
> > Alan L Tyree http://www2.austlii.edu.au/~alan
> > Tel: 04 2748 6206 sip:typhoon@iptel.org
> >
> >
>
>
[-- Attachment #2: Type: text/html, Size: 5206 bytes --]
next prev parent reply other threads:[~2014-01-05 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 22:29 Export each top level heading to separate file Ista Zahn
2014-01-04 22:45 ` Charles Millar
2014-01-04 23:41 ` Alan L Tyree
2014-01-05 0:36 ` Ista Zahn
2014-01-05 2:44 ` Alan L Tyree
2014-01-05 13:40 ` John Kitchin [this message]
2014-01-05 19:49 ` Ista Zahn
2014-01-05 21:56 ` John Kitchin
2014-01-06 0:55 ` Ista Zahn
2014-01-05 18:34 ` Charles Millar
-- strict thread matches above, loose matches on Subject: below --
2014-01-06 1:51 Marvin Doyley
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='CAJ51ETqfUdr9=qCC3QSLhMNsVszhie7eOO_JogS-B-mknPT1mw@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=alantyree@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=istazahn@gmail.com \
/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).