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: Wed, 11 Jan 2017 15:26:51 +0000 [thread overview]
Message-ID: <87bmvdaa84.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <617f560207eb41c0888a6f3c6a8df9db@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (John Kitchin's message of "Tue, 10 Jan 2017 14:27:08 +0000")
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
On Tuesday, 10 Jan 2017 at 14:27, John Kitchin wrote:
> This does not sound right to me.
>
> This org file:
>
> #+BEGIN_SRC org
> ,#+select_tags: wanted
> ,#+exclude_tags: notwanted
>
> ,* headline :notwanted:
> some text
>
> ,** subhead 1
> ,** subhead2 :wanted:
> more text
> #+END_SRC
>
>
> should not have any thing to export.
Yes, and it works. However, if I don't explicitly specify "notwanted"
as excluded, the whole file is exported. I guess I don't understand the
meaning of "select_tags": I would like this to specify those trees to be
exported only if the given tags are present. I would expect the
behaviour to be the same whether I specify excluded tags or not when
selected tags are given, other than exclusion of subtrees within
selected trees.
But I guess my understanding is completely wrong. And re-reading the
documentation doesn't make things clearer for me. There seems to be a
gap between selected and excluded tags which is, to me, ambiguous. If
nothing is specified for either, the documentation implies default
values (:export: and :noexport: respectively). However, the behaviour
is not consistent with this as, if I do not specify any selected or
excluded tags, the default behaviour is to export everything.
I guess I could look at the code to see what the underlying logic really
is. For another day, when I have some time -- it's start of term and
I'm doing the headless chicken impression getting material ready for the
students.
Anyway, with the proper combination of both select and exclude tags, I
have managed to get what I want.
Thanks,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.2-104-gf5b7de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2017-01-11 17:13 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
2017-01-10 14:27 ` John Kitchin
[not found] ` <617f560207eb41c0888a6f3c6a8df9db@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-11 15:26 ` Eric S Fraga [this message]
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=87bmvdaa84.fsf@delle7240.chemeng.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).