From: Bernt Hansen <bernt@norang.ca>
To: Iris Jackson <iris.a.jackson@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Top-level headers in org-sparse-tree
Date: Wed, 10 Sep 2008 10:30:45 -0400 [thread overview]
Message-ID: <87iqt4dqei.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <4faa54dc0809090706o7d756aa9n4b718967c9f26605@mail.gmail.com> (Iris Jackson's message of "Tue\, 9 Sep 2008 10\:06\:01 -0400")
"Iris Jackson" <iris.a.jackson@gmail.com> writes:
> I recently started using org mode and I really like it. I have a single file
> that contains all information about a project like TODOs, project specs, user
> documentation, development notes, etc. For example, the way I generate the
> project specs is to first create a sparse tree matching on the tag I assigned
> to the specs, then HTML exporting it.
>
> The problem I encountered is that org-tags-sparse-tree shows top-level headers
> even if they don't contain the selected tag. Is there a simple way to turn
> that off? For example, if I have a top level section called "Bugs", and it
> does not contain the "project spec" tag, then I don't want it to show up in
> the result :-)
>
> I think this functionality is controlled by org-make-tags-matcher on line 9382
> of org.el (version 6.06b), but this function is too intimidating for me to try
> to change it.
>
> Please advise. Thanks!
You can highlight the region you want to export then
M-x narrow-to-region
Do your export and then
M-x widen
to restrict what is included in the export.
Hope that helps.
-Bernt
next prev parent reply other threads:[~2008-09-10 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 14:06 Top-level headers in org-sparse-tree Iris Jackson
2008-09-10 14:30 ` Bernt Hansen [this message]
2008-09-10 14:40 ` R: " Giovanni Ridolfi
2008-09-10 15:20 ` Giovanni Ridolfi
2008-09-13 16:18 ` Carsten Dominik
2014-11-17 7:54 ` Adam
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iqt4dqei.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=iris.a.jackson@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.