From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: not exporting TODOs but exporting their subordinates Date: Wed, 8 Sep 2010 14:40:46 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0103952430==" Return-path: Received: from [140.186.70.92] (port=46887 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OtQVs-0005J8-Vm for emacs-orgmode@gnu.org; Wed, 08 Sep 2010 15:40:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OtQVq-0006OX-VQ for emacs-orgmode@gnu.org; Wed, 08 Sep 2010 15:40:56 -0400 Received: from mail-bw0-f41.google.com ([209.85.214.41]:41207) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OtQVq-0006OI-Lm for emacs-orgmode@gnu.org; Wed, 08 Sep 2010 15:40:54 -0400 Received: by bwz6 with SMTP id 6so541360bwz.0 for ; Wed, 08 Sep 2010 12:40:53 -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: Sam Cramer Cc: emacs-orgmode@gnu.org --===============0103952430== Content-Type: multipart/alternative; boundary=0016e6d99c1da63b74048fc4b039 --0016e6d99c1da63b74048fc4b039 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Sep 8, 2010 at 2:34 PM, Sam Cramer wrote: > Thanks for your response! > > On Wed, Sep 8, 2010 at 7:23 AM, John Hendy wrote: > >> Someone *might* be able to give you a workaround, but the way org-mode >> works as far as I can see is that export rules always apply to the children >> of a higher-level headline. As such, the subitems of the non-exported TODO >> are taken to be notes or things related to the TODO, and since you don't >> want the TODO exported it would seem that you don't want the items related >> to the TODO exported either. >> >> Maybe if you explain a situation where you'd not want the actual TODO >> exported but still want items under it exported, someone could help you with >> a workaround or alternative suggestion? >> > > 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. 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 >>> >>> >> > --0016e6d99c1da63b74048fc4b039 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Wed, Sep 8, 2010 at 2:34 PM, Sam Cramer <samcramer@gmail.com= > wrote:
Thanks for your response!

On Wed, Sep 8, = 2010 at 7:23 AM, John Hendy <jw.hendy@gmail.com> wrote:
=
Someone might=A0be able to give you a workaround, but the way org-mo= de works as far as I can see is that export rules always apply to the child= ren of a higher-level headline. As such, the subitems of the non-exported T= ODO are taken to be notes or things related to the TODO, and since you don&= #39;t want the TODO exported it would seem that you don't want the item= s related to the TODO exported either.

Maybe if you explain a situation where you'd not want th= e actual TODO exported but still want items under it exported, someone coul= d help you with a workaround or alternative suggestion?

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 t= he overall structure of the file. =A0In other words, my TODOs are generally= "one-liners" which are sprinkled with abandon throughout the fil= e.

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. Perhaps, th= en, the best solution is to just make sure your TODOs have no children, the= n? 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 wo= rks perfectly on export for me.


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




--0016e6d99c1da63b74048fc4b039-- --===============0103952430== 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 --===============0103952430==--