From: Matthew Lundin <mdl@imapmail.org>
To: Eraldo Helal <admin@eraldo.at>
Cc: emacs-orgmode@gnu.org
Subject: Re: Show parent PROJECTS for an item
Date: Sun, 17 May 2009 21:07:49 -0500 [thread overview]
Message-ID: <87k54fyxhm.fsf@fastmail.fm> (raw)
In-Reply-To: <938fae2d0905171518u83cabffh25122428a130e30b@mail.gmail.com> (Eraldo Helal's message of "Mon, 18 May 2009 00:18:22 +0200")
Eraldo Helal <admin@eraldo.at> writes:
> On Sun, May 17, 2009 at 23:25, Matthew Lundin <mdl@imapmail.org> wrote:
>
> Why not use categories for this? You could define a category for
> each
> project:
>
> --8<---------------cut here---------------start------------->8---
> ** Some Project
> :PROPERTIES:
> :CATEGORY: special project
> :END:
> *** TODO Testing
> --8<---------------cut here---------------end--------------->8---
>
> Would show up in the agenda as:
>
> --8<---------------cut here---------------start------------->8---
> special project:TODO Testing
> --8<---------------cut here---------------end--------------->8---
>
> Sounds line a good idea, but:...
> Doubts:
> 1. I would have to set that prop for each project headline. // a lot of
> work
More work than adding the project name to each todo by hand, as your
original post proposed?
> 2. It is prone to "errors" > renaming the project does not rename the
> context, etc.
In my opinion, the easiest way to figure out which project a TODO
belongs to is to use follow mode in the agenda. That way you can see the
original context (i.e., project) to which a todo belongs.
- Matt
next prev parent reply other threads:[~2009-05-18 2:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 21:33 Show parent PROJECTS for an item Marcelo de Moraes Serpa
2009-05-16 15:11 ` Carsten Dominik
2009-05-17 20:58 ` Eraldo Helal
2009-05-17 21:25 ` Matthew Lundin
2009-05-17 22:18 ` Eraldo Helal
2009-05-18 2:07 ` Matthew Lundin [this message]
2009-05-18 9:18 ` Eraldo Helal
2009-05-18 15:52 ` Marcelo de Moraes Serpa
2009-05-18 16:21 ` Samuel Wales
2009-05-18 22:01 ` Eraldo Helal
2009-05-18 22:16 ` Samuel Wales
2009-05-18 22:47 ` Eraldo Helal
2009-05-18 23:01 ` Eraldo Helal
2009-05-19 3:01 ` Manish
2009-05-19 15:48 ` Eraldo Helal
2009-05-19 21:27 ` Marcelo de Moraes Serpa
2009-05-19 22:06 ` Eraldo Helal
2009-05-19 22:29 ` Matthew Lundin
2009-05-19 22:55 ` Eraldo Helal
2009-05-19 23:06 ` Marcelo de Moraes Serpa
2009-05-20 4:52 ` Carsten Dominik
2009-05-20 1:52 ` Nick Dokos
2009-05-20 4:20 ` Manish
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=87k54fyxhm.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=admin@eraldo.at \
--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).