From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Scott Randby <srandby@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Leading headline of a subtree tag export
Date: Wed, 11 Dec 2013 16:57:07 +0100 [thread overview]
Message-ID: <87eh5jxtws.fsf@gmail.com> (raw)
In-Reply-To: <52A88811.8070505@gmail.com> (Scott Randby's message of "Wed, 11 Dec 2013 10:43:13 -0500")
Hello,
Scott Randby <srandby@gmail.com> writes:
> I had a file with the following structure:
>
> #+OPTIONS: tags:nil
> * Grades
> ** Student :studenttag:
> :PROPERTIES:
> :EXPORT_FILE_NAME: Exported-Grades/studenttag
> :END:
> *** Totals :totals:
> Content
>
> Whenever I exported the entire file, no tags were exported (what I
> want). However, whenever I exported the Student subtree, the tag for
> that subtree was exported (not what I want) but the tag for the Totals
> subtree was not exported (what I want). Then I tried the following:
>
> #+OPTIONS: tags:nil
> * Grades
> ** Student :studenttag:
> :PROPERTIES:
> :EXPORT_FILE_NAME: Exported-Grades/studenttag
> :EXPORT_OPTIONS: tags:nil
> :END:
> *** Totals :totals:
> Content
>
> The tag for the Student subtree is still exported when I export the
> Student subtree. How do I prevent this tag from being exported when I
> export the subtree?
During a subtree export, the root headline becomes document's title, so
tags:nil no longer applies. By default everything is included, todo
keyword and tags.
You can specify another title with :EXPORT_TITLE:, e.g.
:EXPORT_TITLE: Student
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-12-11 15:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 17:46 publishuing in html5 Catonano
2013-12-09 17:59 ` Catonano
2013-12-09 18:48 ` Catonano
2013-12-09 19:53 ` Nick Dokos
2013-12-11 0:41 ` Scott Randby
2013-12-11 12:58 ` Nick Dokos
2013-12-11 14:13 ` Scott Randby
2013-12-11 15:04 ` Nick Dokos
2013-12-11 15:20 ` Scott Randby
2013-12-11 15:24 ` Nicolas Goaziou
2013-12-11 15:47 ` Scott Randby
2013-12-11 16:03 ` Nicolas Goaziou
2013-12-11 16:30 ` Scott Randby
2013-12-14 17:01 ` Catonano
2013-12-14 19:40 ` Nick Dokos
2013-12-14 21:22 ` Alan L Tyree
2013-12-14 21:36 ` Achim Gratz
2013-12-18 10:16 ` Catonano
2013-12-18 16:41 ` Nick Dokos
2013-12-31 11:31 ` Catonano
2013-12-31 12:47 ` Catonano
2013-12-31 16:41 ` Nick Dokos
2013-12-15 10:00 ` Nicolas Goaziou
2013-12-15 18:30 ` Scott Randby
2013-12-11 15:43 ` Leading headline of a subtree tag export Scott Randby
2013-12-11 15:57 ` Nicolas Goaziou [this message]
2013-12-11 16:35 ` Scott Randby
2013-12-11 10:00 ` publishuing in html5 Catonano
2013-12-09 19:57 ` Nicolas Goaziou
2013-12-11 9:56 ` Catonano
2013-12-15 10:07 ` Nicolas Goaziou
2013-12-18 10:04 ` Catonano
2013-12-18 13:02 ` Nicolas Goaziou
2013-12-31 11:06 ` Catonano
2013-12-20 20:06 ` Scott Randby
2013-12-31 11:42 ` Catonano
2013-12-31 11:47 ` Catonano
2013-12-31 16:28 ` Nick Dokos
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=87eh5jxtws.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=srandby@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 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).