From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: Automatic noexport tag based on rules? Date: Tue, 8 Feb 2011 20:39:54 -0600 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1823699232==" Return-path: Received: from [140.186.70.92] (port=38178 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PmzyH-0000i5-Tv for emacs-orgmode@gnu.org; Tue, 08 Feb 2011 21:39:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PmzyF-0002bj-Rx for emacs-orgmode@gnu.org; Tue, 08 Feb 2011 21:39:57 -0500 Received: from mail-bw0-f41.google.com ([209.85.214.41]:35121) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PmzyF-0002bY-F0 for emacs-orgmode@gnu.org; Tue, 08 Feb 2011 21:39:55 -0500 Received: by bwz16 with SMTP id 16so507431bwz.0 for ; Tue, 08 Feb 2011 18:39:54 -0800 (PST) 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: Jeff Horn Cc: emacs-orgmode --===============1823699232== Content-Type: multipart/alternative; boundary=0016e6d7df4042d38b049bd0618b --0016e6d7df4042d38b049bd0618b Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 8, 2011 at 7:58 PM, Jeff Horn wrote: > I'm not handy with emacs-lisp, but perhaps someone could whip up a > handy function that iterates org-refile over each TODO heading to move > it into a new, top-level * Tasks headline? > > Thanks for the suggestion. I'm not a huge fan, but it would get done what I want to accomplish as far as the export goes. > Then you can tag the tasks headline with :noexport:. This would > destroy the "context", but I find keeping tasks in a separate heading > fine for most of *my* medium sized projects. YMMV. > Yeah.. most of my todos aren't medium-sized projects, though. Many of them are more along the lines of one-liner action items I need to jot to myself so I don't forget as well as keeping them as a sort of rolling "next actions" queue. For that reason, I'd much rather keep them in their original context. This can't be too hard. ,--- | sed '/[*]* TODO/ s/$/ :noexport:/g' `--- Or (facetious) ,--- | setq (prefix-for-noexport-custom-variable) | setq (default-tags-for-no-export-variable) `--- I just don't know what the elegant, "right" elisp/org method is for something like this. John > On Tue, Feb 8, 2011 at 7:29 PM, John Hendy wrote: > > Hi, > > > > My apologies if this has been discussed. I couldn't find it. I write > > everything from work in org-mode for several reasons. Primarily, it's my > > documentation system for research in order to properly document > Intellectual > > Property (IP) information. It's also for todos and contacts. When it > comes > > to exporting my notes into PDF for use in an IP notebook... I dont' want > my > > todos in there. > > Is there a way to automatically tag TODOs with :noexport:? > > Or simply add the TODO category to the noexport category altogether? > > I haven't turned up anything quite along these lines. One post suggested > > using "TODO keyword COMMENT" [1], but that just seems to perhaps exclude > > from export (didn't try) but I know for sure it removes it from agenda > view. > > I want TODOs in agenda but don't want them showing up with my LaTeX > export. > > I typically print out my work to-date each month or so and have to comb > > through my org file for that month, manually adding :noexport: to my > TODOs. > > Even if I still do this for a few things here and there... it will save > me a > > lot of time. > > I suppose I could keep a separate "TODO.org" file, but I really like the > > process of being able to add them anywhere -- it seems more natural to do > > that in the flow, particularly in meetings, than to constantly switch > > buffers or even use remember to keep sending things related to the > current > > topic away to their own island. > > I'm 80% confident that the answer is ridiculously simply and I just > haven't > > searched the right thing. Thanks for enlightening me! > > > > Thanks, > > John > > _______________________________________________ > > 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 > > > > > > > > -- > Jeffrey Horn > http://www.failuretorefrain.com/jeff/ > --0016e6d7df4042d38b049bd0618b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Feb 8, 2011 at 7:58 PM, Jeff Horn <jrhorn424@gmail.com<= /a>> wrote:
I'm not handy with emacs-lisp, but perhaps someone could whip up a
handy function that iterates org-refile over each TODO heading to move
it into a new, top-level * Tasks headline?


Thanks for the suggestion. I'm not= a huge fan, but it would get done what I want to accomplish as far as the = export goes.
=A0
Then you can tag the tasks headline with :noexport:. This would
destroy the "context", but I find keeping tasks in a separate hea= ding
fine for most of *my* medium sized projects. YMMV.
Yeah.. most of my todos aren't medium-sized projects, thoug= h. Many of them are more along the lines of one-liner action items I need t= o jot to myself so I don't forget as well as keeping them as a sort of = rolling "next actions" queue. For that reason, I'd much rathe= r keep them in their original context.

This can't be too hard.

,-= --
| sed '/[*]* TODO/ s/$/ =A0 :noexport:/g'
`-= --

Or (facetious)

,---
| setq (prefix-for-noexport-custom-variable)
| setq (default= -tags-for-no-export-variable)
`---

I jus= t don't know what the elegant, "right" elisp/org method is fo= r something like this.


John


=


On Tue, Feb 8, 2011 at 7:29 PM, John Hendy <jw.hendy@gmail.com> wrote:
> Hi,
>
> My apologies if this has been discussed. I couldn't find it. I wri= te
> everything from work in org-mode for several reasons. Primarily, it= 9;s my
> documentation system for research in order to properly document Intell= ectual
> Property (IP) information. It's also for todos and contacts. When = it comes
> to exporting my notes into PDF for use in an IP notebook... I dont'= ; want my
> todos in there.
> Is there a way to automatically tag TODOs with :noexport:?
> Or simply add the TODO category to the noexport category altogether? > I haven't turned up anything quite along these lines. One post sug= gested
> using "TODO keyword COMMENT" [1], but that just seems to per= haps exclude
> from export (didn't try) but I know for sure it removes it from ag= enda view.
> I want TODOs in agenda but don't want them showing up with my LaTe= X export.
> I typically print out my work to-date each month or so and have to com= b
> through my org file for that month, manually adding :noexport: to my T= ODOs.
> Even if I still do this for a few things here and there... it will sav= e me a
> lot of time.
> I suppose I could keep a separate "TODO.org" file, but I rea= lly like the
> process of being able to add them anywhere -- it seems more natural to= do
> that in the flow, particularly in meetings, than to constantly switch<= br> > buffers or even use remember to keep sending things related to the cur= rent
> topic away to their own island.
> I'm 80% confident that the answer is ridiculously simply and I jus= t haven't
> searched the right thing. Thanks for enlightening me!
>
> Thanks,
> John
> _______________________________________________
> 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
>
>



--
Jeffrey Horn
http://= www.failuretorefrain.com/jeff/

--0016e6d7df4042d38b049bd0618b-- --===============1823699232== 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 --===============1823699232==--