emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Piotr Zielinski" <piotr.zielinski@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org, Frank Ruell <stoerte@dreamwarrior.net>
Subject: Re: checkable items which don't show up in agenda
Date: Wed, 26 Apr 2006 14:08:06 +0100	[thread overview]
Message-ID: <3c12eb8d0604260608l586c2b88udb68c5d7885640d1@mail.gmail.com> (raw)
In-Reply-To: <679cece820913c1b5db5903c83b6c0d3@science.uva.nl>

Hi,

It seems that different people use TODOs in different ways.  For
example, I use TODOs at the very lowest possible level to indicate the
next action in a particular project.  That said, I'd welcome some
hierarchical propagation of TODO, as it is with tags.  One can imagine
using two kinds of todos: TODO and NEXTACTION.  TODO would be attached
to (high-level) projects I'm currently interested in doing, whereas
NEXTACTION attached to the low-level nodes of the tree that correspond
to the next physical action to take.  The agenda could be configured
in such a way to display only these NEXTACTIONs that have an ancestor
marked as TODO.  Note that this is already possible with tags.  Is it
sensible to make org.el treat TODOs as a any other tag?

To make most of org-mode, I think it would be very useful to compare
how people actually use it.  I'm sure I could learn a lot of useful
things from such an exchange, and would be surprised by the variety of
organizing structures people use.  The best way to achieve that is
probably to post deprivatized sample parts of our .org files with a
short explanation.  What place do you think is the best: this email
list? some wiki? something else?

Piotr

On 26/04/06, Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
> 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.
>
> Interesting idea.  I could make an option which would stop searching
> for TODO in the subtree below a TODO entry.
>
> - Carsten
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

  reply	other threads:[~2006-04-26 13:08 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 [this message]
2006-04-26 13:54       ` org-mode usage patterns David O'Toole
2006-04-26 13:48     ` checkable items which don't show up in agenda Frank Ruell

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=3c12eb8d0604260608l586c2b88udb68c5d7885640d1@mail.gmail.com \
    --to=piotr.zielinski@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=stoerte@dreamwarrior.net \
    /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).