From: John Kitchin <jkitchin@andrew.cmu.edu>
To: simon@psilas.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Separate Org file from Subtree
Date: Mon, 16 Feb 2015 07:54:46 -0500 [thread overview]
Message-ID: <m28ufyow2x.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <1424083270.1791871.228021221.7DB94916@webmail.messagingengine.com>
Change :EXPORT_FILENAME: an-interesting-article to :EXPORT_FILE_NAME:
an-interesting-article
Then,
C-c C-e C-s O o
should export to that file. I notice in the org export that the
properties are not getting exported, and even the headline is not
exported as the title though.
Here is a function that seems to do what you want.
#+BEGIN_SRC emacs-lisp
(defun export-subtree ()
(interactive)
(let ((fname (concat (org-entry-get (point) "EXPORT_FILE_NAME") ".org"))
(author (org-entry-get (point) "EXPORT_AUTHOR"))
(title (org-entry-get (point) "EXPORT_TITLE"))
(date (org-entry-get (point) "EXPORT_DATE"))
(content (progn (set-buffer (org-org-export-as-org nil t t))
(buffer-string))))
;; warning you can delete something unintentionally
(when (file-exists-p fname) (delete-file fname))
(find-file fname)
(insert "#+TITLE: " title "\n")
(insert "#+AUTHOR: " author "\n")
(insert "#+DATE: " date "\n")
(insert "\n" content)
;; remove properties drawer. Kind of hacky.
(goto-char (point-min))
(re-search-forward ":PROPERTIES:")
(setf (buffer-substring
(org-element-property :begin (org-element-context))
(org-element-property :end (org-element-context)))
"")
(save-buffer)))
(export-subtree)
#+END_SRC
simon@psilas.com writes:
> Hi there,
>
> I think I must be missing something.
>
> I have a collection of articles in one org file (under separate
> headings). I can export these as a subtree using Org's normal export
> function as html etc., but I want to export the selected subtree as an
> individual org file using the properties under each heading.)
>
> In other words I want to export this subtree ...
> * DONE Article One
> :PROPERTIES:
> :EXPORT_TITLE: An Interesting Article
> :EXPORT_AUTHOR: Simon Jones
> :EXPORT_FILENAME: an-interesting-article
> :EXPORT_DATE: 2015-02-16
> :END:
>
> Article content ....
>
> into an Org file entitled 'an-interesting-article.org' that looks like
> this ...
>
> #+TITLE: An Interesting Article
> #+AUTHOR: Simon Jones
> #+DATE: 2015-02-16
>
> Article content...
>
> Can anyone help me with this? I'm very sorry if I'm missing something
> obvious.
>
> Simon.
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-02-16 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 10:41 Separate Org file from Subtree simon
2015-02-16 12:54 ` John Kitchin [this message]
2015-02-16 14:40 ` simon
2015-02-16 14:59 ` John Kitchin
2015-02-16 15:30 ` simon
2015-08-05 0:00 ` Bastien Guerry
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=m28ufyow2x.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=simon@psilas.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).