From: Sebastian Rose <sebastian_rose@gmx.de>
To: Sam Cramer <samcramer@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: not exporting TODOs but exporting their subordinates
Date: Wed, 08 Sep 2010 18:14:40 +0200 [thread overview]
Message-ID: <87occ8b4b3.fsf@gmx.de> (raw)
In-Reply-To: <AANLkTimcdexOz2zprULC7Ju4==ztdQzKSm8QMJ0zuN-2@mail.gmail.com> (Sam Cramer's message of "Tue, 7 Sep 2010 19:28:54 -0700")
Sam Cramer <samcramer@gmail.com> writes:
> When working on a document, I tend to sprinkle TODO headlines throughout the
> doc. These are really very loosely structured; they just represent things
> that I need to do somewhat near the area that I'm looking at.
>
> I mark these lines with a :noexport: tag in order to prevent them from being
> exported. As such, they're not part of the document structure per-se, and I
> often mark them as top level headlines. Since EXPORT_EXCLUDE_TAGS applies
> to a tree and not to a title, this prevents the export of any subordinate
> items.
>
> Here's an example:
>
> * An amazing headline
> ** stuff
> ** more stuff
> * TODO clean up the stuff above :noexport:
> ** this is stuff that I would like exported
>
>
> In the example above, I'd like to have the everything but the TODO headline
> exported, including the "this is stuff I would like exported" line.
>
> I guess that I could always have my TODO lines be at a very deep level. Is
> there any other solution I should consider?
>
> Thanks,
> Sam
Here's my proposal:
* An amazing headline
** stuff
** more stuff
******* TODO clean up the stuff above :noexport:
** this is stuff that I would like exported
Or just use inline tasks. They are made for this purpose.
Sebastian
next prev parent reply other threads:[~2010-09-08 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 2:28 not exporting TODOs but exporting their subordinates Sam Cramer
2010-09-08 14:23 ` John Hendy
2010-09-08 19:34 ` Sam Cramer
2010-09-08 19:40 ` John Hendy
2010-09-08 20:21 ` Sam Cramer
2010-09-08 16:14 ` Sebastian Rose [this message]
2010-09-08 19:36 ` Sam Cramer
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=87occ8b4b3.fsf@gmx.de \
--to=sebastian_rose@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=samcramer@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).