From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Limit subtree to a specific export backend
Date: Fri, 04 Oct 2013 09:21:29 +0200 [thread overview]
Message-ID: <86txgxcxhi.fsf@somewhere.org> (raw)
In-Reply-To: CALf2awR93+P9+iy-o0BuNQm8nQczzuyCBkz2OY89KYU2n+r7ig@mail.gmail.com
Hi Sebastian,
Sebastian Wiesner wrote:
> 2013/9/30 Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>:
>> A partly manual solution would be to use tags for which sections to export
>> in which backend, make a sparse tree with the backend you're interested to
>> export, and export what's visible?
>
> I am by far not an Org mode expert, and have never used sparse trees. Would
> you mind to point me to the appropriate manual section, or give me some
> details on how to create a sparse tree matching a specific tag only?
See section 2.6 Sparse trees:
╭────
│ An important feature of Org mode is the ability to construct _sparse
│ trees_ for selected information in an outline tree, so that the entire
│ document is folded as much as possible, but the selected information is
│ made visible along with the headline structure above it(1). Just try
│ it out and you will see immediately how it works.
│
│ Org mode contains several commands creating such trees, all these
│ commands can be accessed through a dispatcher:
│
│ `C-c /' (`org-sparse-tree')
│ This prompts for an extra key to select a sparse-tree creating
│ command.
╰────
It will help to "expand" all entries which contain a certain keyword (see `C-c
/ /') and "collapse" all others. Though, it won't help for tagged entries:
their contents won't be opened automatically by doing `C-c / m' (match for a
tag).
Anyway, `C-c /' is a very interesting (set of) commands to know!
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-10-04 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 14:06 Limit subtree to a specific export backend Sebastian Wiesner
2013-09-30 14:24 ` Sebastien Vauban
2013-10-03 22:27 ` Sebastian Wiesner
2013-10-04 7:21 ` Sebastien Vauban [this message]
2013-09-30 16:03 ` Rasmus
2013-10-04 10:33 ` Sebastian Wiesner
2013-10-04 12:36 ` Rasmus
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=86txgxcxhi.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).