emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Automatic noexport tag based on rules?
Date: Fri, 25 Feb 2011 16:37:13 -0600	[thread overview]
Message-ID: <AANLkTinmKtVzFOPK9zbr9C4gmD48ONpLdZDM1MnQKJZH@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimJK63-O7sAOpjVwKcUMaL1hMbtvpZJUq90m+xi@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3176 bytes --]

Reviving this as I can't believe the following solution was overlooked!

On Tue, Feb 8, 2011 at 6:29 PM, John Hendy <jw.hendy@gmail.com> 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:?
>
>
YES! While perusing Bernt Hanson's page (
http://doc.norang.ca/org-mode.html#ToDoStateTriggers) I noticed the
following:
,-----
| I have a few triggers that automatically assign tags to tasks based on
| state changes. If a task moves to CANCELLED state then it gets a CANCELLED
 tag.
| Moving a CANCELLED task back to TODO removes the CANCELLED tag.
| These are used for filtering tasks in agenda views which I'll talk about
later.
| ... then he shows the code used to set =org-todo-state-tags-triggers=
`-----

Sweetness, I thought. In experimenting:
,-----
| (setq org-todo-state-tags-triggers
|      (quote (("TODO" ("noexport" . t)))))
`-----

works *perfectly*. Well, that is in my 0.2 seconds of experimentation, it
worked. New headline -> C-c C-t -> ** TODO whatever :noexport:

I'm a happy camper.  I had resolved to arranging my file with a separate =*
Tasks= top level item at the top of each file to store all todos (I may
still do this) and then I could just tag the whole headline with :noexport:
to keep all the todos out of the export since I'm often typing notes or
something and the TODO seems to fit better in the context of the notes
rather than having to stuff it into a bucket at the top with TODOs from all
kinds of other stuff.. At least if I don't do this, I have some options.
Adding a todo in place will keep it from being exported when I print out my
reports.

The world is safe again...


Best regards,
John

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
>

[-- Attachment #1.2: Type: text/html, Size: 5598 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

  parent reply	other threads:[~2011-02-25 22:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09  0:29 Automatic noexport tag based on rules? John Hendy
2011-02-09  1:58 ` Jeff Horn
2011-02-09  2:39   ` John Hendy
2011-02-09  2:53     ` Jeff Horn
2011-02-09  7:40     ` Eric S Fraga
2011-02-09 15:18       ` John Hendy
2011-02-09 16:58         ` John Hendy
2011-02-09 18:13       ` Nicolas Goaziou
2011-02-09 18:46         ` John Hendy
2011-02-09  9:36     ` Automatic noexport tag based on rules? (and a possible bug) Nick Dokos
2011-02-11  8:34 ` Automatic noexport tag based on rules? Carsten Dominik
2011-02-11 15:33   ` John Hendy
2011-02-25 22:37 ` John Hendy [this message]
2011-03-27 19:37   ` [Orgmode] " Samuel Wales
2011-03-27 20:10     ` John Hendy
2011-03-29 18:40       ` Matt Lundin
2011-03-29 21:05         ` Carsten Dominik
2011-03-29 21:15           ` Carsten Dominik
2011-03-29 21:48             ` John Hendy
2011-03-29 22:49               ` Carsten Dominik
2011-03-29 22:50                 ` John Hendy
2011-03-30  3:30                   ` Carsten Dominik

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=AANLkTinmKtVzFOPK9zbr9C4gmD48ONpLdZDM1MnQKJZH@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).