From: Sam Cramer <samcramer@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: not exporting TODOs but exporting their subordinates
Date: Wed, 8 Sep 2010 13:21:05 -0700 [thread overview]
Message-ID: <AANLkTik2_jWvph3K+JMbu1kJC8Y4rasdXUDx85HzG8SU@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=Em+z=V0svyvP+_Ku0KMZP22bgo0MLY4VxbOk9@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3088 bytes --]
On Wed, Sep 8, 2010 at 12:40 PM, John Hendy <jw.hendy@gmail.com> wrote:
> On Wed, Sep 8, 2010 at 2:34 PM, Sam Cramer <samcramer@gmail.com> wrote:
>
>>
>> The situation is one that arguably results from a lack of discipline on my
>> part (hence my interest in org-mode!): I add TODO items to documents I'm
>> writing without much regard as to how they fit into the overall structure of
>> the file. In other words, my TODOs are generally "one-liners" which are
>> sprinkled with abandon throughout the file.
>>
>> Perhaps as I get more familiar with org-mode I will use TODOs in a more
>> structured way, but right now they are not a structured list of tasks but
>> rather a bunch of reminders distributed through a document.
>>
>> Does that make things clearer?
>>
>>
> It does make things clearer. Perhaps, then, the best solution is to just
> make sure your TODOs have no children, then? Or use the other suggestion for
> inline TODOs?
>
> In your example, for example, wouldn't this work?
>
> --------
> * An amazing headline
> ** stuff
> ** more stuff
> ** TODO clean up the stuff above :noexport:
> ** this is stuff that I would like exported
> --------
>
> The TODO was directed at the stuff above anyway, so it perhaps doesn't need
> to be it's own main headline? The above works perfectly on export for me.
>
Yes, that works too. The only caveat is that if I later add a subordinate
item to "more stuff" under the TODO, it won't export. Org-inlinetask.el or
simply making the TODOs deeply nested without the help of org-inlinetask
should solve that problem.
Thanks again for the help!
Sam
>
>
> John
>
>
>> Sam
>>
>>
>>
>>>
>>>
>>> John
>>>
>>> On Tue, Sep 7, 2010 at 9:28 PM, Sam Cramer <samcramer@gmail.com> wrote:
>>>
>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Emacs-orgmode mailing list
>>>> Please use `Reply All' to send replies to the list.
>>>> Emacs-orgmode@gnu.org
>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>>
>>>>
>>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 5895 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-09-08 20:21 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 [this message]
2010-09-08 16:14 ` Sebastian Rose
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=AANLkTik2_jWvph3K+JMbu1kJC8Y4rasdXUDx85HzG8SU@mail.gmail.com \
--to=samcramer@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@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).