From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Cramer Subject: Re: not exporting TODOs but exporting their subordinates Date: Wed, 8 Sep 2010 13:21:05 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1530942854==" Return-path: Received: from [140.186.70.92] (port=54206 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OtR8m-0005Bq-6s for emacs-orgmode@gnu.org; Wed, 08 Sep 2010 16:21:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OtR8k-0004eH-Pl for emacs-orgmode@gnu.org; Wed, 08 Sep 2010 16:21:08 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:62416) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OtR8k-0004eB-Ge for emacs-orgmode@gnu.org; Wed, 08 Sep 2010 16:21:06 -0400 Received: by wyb36 with SMTP id 36so536378wyb.0 for ; Wed, 08 Sep 2010 13:21:05 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: John Hendy Cc: emacs-orgmode@gnu.org --===============1530942854== Content-Type: multipart/alternative; boundary=0016368330accacd10048fc54082 --0016368330accacd10048fc54082 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Sep 8, 2010 at 12:40 PM, John Hendy wrote: > On Wed, Sep 8, 2010 at 2:34 PM, Sam Cramer 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 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 >>>> >>>> >>> >> > --0016368330accacd10048fc54082 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 resu= lts 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. =A0In other words, my TOD= Os are generally "one-liners" which are sprinkled with abandon th= roughout 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 li= st of tasks but rather a bunch of reminders distributed through a document.=

Does that make things clearer?


It does make things clearer. Perha= ps, then, the best solution is to just make sure your TODOs have no childre= n, then? Or use the other suggestion for inline TODOs?

In your example, for example, wouldn't this work?

--------
* An amaz= ing headline
** stuff
** more stuff
** TODO c= lean up the stuff above :noexport:
** this is stuff that I would like exported
----= ----

The TODO was directed at the stuff above anyw= ay, so it perhaps doesn't need to be it's own main headline? The ab= ove works perfectly on export for me.

Yes, that works too. =A0The only cav= eat is that if I later add a subordinate item to "more stuff" und= er the TODO, it won't export. =A0Org-inlinetask.el or simply making the TODOs deepl= y nested without the help of org-inlinetask should solve that problem.

Thanks again for the help!

Sam


John
=A0
Sam

=A0


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 th= e doc. =A0These are really very loosely structured; they just represent thi= ngs that I need to do somewhat near the area that I'm looking at. =A0
I mark these lines with a :noexport: tag in order to prevent= them from being exported. =A0As such, they're not part of the document= structure per-se, and I often mark them as top level headlines. =A0Since E= XPORT_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 headl= ine
** stuff
** more stuff
* TODO clean up the stuff above :noexport:
** this is stuff = that I would like exported

In the exa= mple above, I'd like to have the everything but the TODO headline expor= ted, 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. =A0Is 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@gn= u.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode





--0016368330accacd10048fc54082-- --===============1530942854== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============1530942854==--