From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: excluding whole trees on export when subtrees have "select" tags present
Date: Mon, 09 Jan 2017 21:49:41 +0000 [thread overview]
Message-ID: <87a8azkioa.fsf@ucl.ac.uk> (raw)
In-Reply-To: <b3655cb7d021410f872939e0fedfee6a@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (John Kitchin's message of "Mon, 9 Jan 2017 15:46:58 +0000")
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On Monday, 9 Jan 2017 at 15:46, John Kitchin wrote:
> Based on the docstrings for org-export-select-tags and
> org-export-exclude-tags, this looks expected.
>
> It does not look possible to exclude a heading and include a subheading
> under it. It is possible to include a heading and exclude some
> subheadings though you need a wanted tag in the parent, and notwanted
> tags in the subtrees, and to declare the exclude tags.
I think I was unclear. My confusion is that a tree (rooted at a top
level headline) that I do not want exported is nevertheless exported if
a subtree within that tree has a "selected" tag. I would have thought
the higher level heading would take precedence.
> I am surprised you can use comment like this. It looks to me like
> commenting a tree makes all the subtrees in it not export too.
Yes, it is. Again, I obviously didn't explain myself well. I have
resorted to commenting out whole trees (rooted at headlines) to avoid
them being exported because a sub-tree has the selected tag.
In any case, I have found a workaround by inverting my tag usage.
thanks,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.3-189-ge46676
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2017-01-09 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 9:48 excluding whole trees on export when subtrees have "select" tags present Eric S Fraga
2017-01-09 15:46 ` John Kitchin
[not found] ` <b3655cb7d021410f872939e0fedfee6a@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-09 21:49 ` Eric S Fraga [this message]
2017-01-10 14:27 ` John Kitchin
[not found] ` <617f560207eb41c0888a6f3c6a8df9db@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-11 15:26 ` Eric S Fraga
2017-01-11 20:26 ` Nicolas Goaziou
[not found] ` <af9636231a6b44598ee8e17caee8e941@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-12 6:50 ` Eric S Fraga
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=87a8azkioa.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).