emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Frank Ruell <stoerte@dreamwarrior.net>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: checkable items which don't show up in agenda
Date: Wed, 26 Apr 2006 15:48:47 +0200	[thread overview]
Message-ID: <sapereaude87lktsbg74.fsf@sisyphos.foobar.ath.cx> (raw)
In-Reply-To: <679cece820913c1b5db5903c83b6c0d3@science.uva.nl> (Carsten Dominik's message of "Wed, 26 Apr 2006 11:39:15 +0200")

Carsten Dominik <carsten.dominik@gmail.com> writes:

> On Apr 26, 2006, at 8:54, Christian Egli wrote:
>
>> On Tue, 2006-04-25 at 18:19 +0200, Frank Ruell wrote:
>>> The only thing I've missed was an option for items, which are
>>> fontyfied
>>> and checkable via some shortcut, but never ever show up in agenda (or
>>> rather clutter up your agenda).
>>
>> What would be a use case for that? I have been thinking I would not
>> want
>> to see TODO items in the agenda that for the following scenario:
>>
>> * TODO Organize event
>> ** TODO Choose a date
>> ** TODO Invite people
>>
>> Here I'd like my agenda to remind me only that I need to Organize the
>> event. I'd like to be able to check of the subtasks (which I'll do in
>> the org-mode buffer, not in the agenda), but I do not want them to
>> "clutter" my agenda.

even more extreme:

** TODO Phone people and invite them
*** TODO invite aunt Minna
*** TODO invite uncle Ernst
*** TODO invite great uncle Karl

Workflow: thinking of 25 guys to invite, phoning those guys, and then
keeping track of who you did or did not reach.

(Last actual use case for me was when doing homework, I've read the
exercise, wrote a list of classes and methods while doing so, and then,
when actually programming, it would have been nice to be able to check
the finished stuff. Identical to the way I would have done it with
pencil and paper.)

> Interesting idea.  I could make an option which would stop searching
> for TODO in the subtree below a TODO entry.

For the "invite example" above I wouldn't even like to give each one his
own heading. (For those "checklets" I used C-u for not changing into
heading). Nor would I want those subitems to be "prominent fontyfied" as
TODOs are. Like for inviting a bunch of people I would consider just one
TODO the most adequate way.
Of course in most cases everything but splitting a TODO into smaller
TODOs would be confusing and bloat.


cheers,
Frank
-- 
IRRELIGION, n.  The principal one of the great faiths of the world.
(Ambrose Bierce, The Devil's Dictionary)

      parent reply	other threads:[~2006-04-26 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 16:19 checkable items which don't show up in agenda Frank Ruell
2006-04-26  6:54 ` Christian Egli
2006-04-26  9:39   ` Carsten Dominik
2006-04-26 13:08     ` Piotr Zielinski
2006-04-26 13:54       ` org-mode usage patterns David O'Toole
2006-04-26 13:48     ` Frank Ruell [this message]

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=sapereaude87lktsbg74.fsf@sisyphos.foobar.ath.cx \
    --to=stoerte@dreamwarrior.net \
    --cc=carsten.dominik@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).