From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: Export subtrees of level n
Date: Sun, 03 Sep 2017 03:13:42 -0500 [thread overview]
Message-ID: <87d178dwsp.fsf@alphapapa.net> (raw)
In-Reply-To: 8737846w8s.fsf@luisa.c0t0d0s0.de
Michael Welle <mwe012008@gmx.net> writes:
> Is there an existing way to say that I want to go up to a level n
> heading and then export, or do I have to implement that by myself?
I think you'll have to do it yourself. Here are a couple of ideas:
1. Write a function to export a subtree with a specific Org ID.
2. Write a function to look up the tree from point and export the first
subtree with a certain property.
next prev parent reply other threads:[~2017-09-03 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 8:07 Export subtrees of level n Michael Welle
2017-09-03 8:12 ` Nicolas Goaziou
2017-09-03 8:18 ` Michael Welle
2017-09-03 8:13 ` Adam Porter [this message]
2017-09-03 8:23 ` Michael Welle
2017-09-03 17:26 ` Joon Ro
2017-09-03 18:20 ` Michael Welle
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=87d178dwsp.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--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).