From: tsd@tsdye.com (Thomas S. Dye)
To: M <Elwood151@web.de>
Cc: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
Subject: Re: How to deal with small projects which are often changing their status/ person
Date: Tue, 22 Jan 2013 12:49:20 -1000 [thread overview]
Message-ID: <m1libk6dfz.fsf@tsdye.com> (raw)
In-Reply-To: <CD24D0D6.13D25%Elwood151@web.de> (M.'s message of "Tue, 22 Jan 2013 23:27:18 +0100")
M <Elwood151@web.de> writes:
> Hi Thomas,
>
> thanks for your reply!
>
> Sure I know Bernt Hansen's web page and I'm already using his configuration
> for my system. (I'm still learning Emacs and org-mode, so it was easier to
> start with an existing setup).
>
> I already know and use the capture and refile feature,
> my problem is that I have the feeling to do more administration of tasks
> than really doing them if I track such projects like the one described with
> org-mode and create a sub-task for each step.
> Especially as I'd have to re-type each time again the name of the project if
> I want it to appear in my agenda explicitly and not only:
> WAITING John: Feedback
> (and I would not know which text it is about).
Good news. With Bernt's setup you are off to a good start.
Perhaps Properties will do what you want? These are inherited by
sub-trees, so they will follow Task 1, Task 2, etc.
* Topic XYZ
:PROPERTIES:
:CATEGORY: XYZ
:END:
** DONE Task 1
** TODO Task 2
The CATEGORY property shows up in my Agenda, so I would know that Task 2
belonged to XYZ.
This is how I manage the dozen or so open work projects I have at any
one time. We assign each project a number, which I put in the CATEGORY
property. When I generate my daily agenda, I see the project number
beside each TODO task.
See Chapter 7 of the manual for details.
hth,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
next prev parent reply other threads:[~2013-01-22 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 20:19 How to deal with small projects which are often changing their status/ person M
2013-01-22 21:14 ` Thorsten Jolitz
2013-01-22 21:39 ` Nicolas Richard
2013-01-22 21:56 ` Thorsten Jolitz
2013-01-22 21:40 ` M
2013-01-22 21:55 ` Thorsten Jolitz
2013-01-23 8:59 ` Tomas Hlavaty
2013-01-23 10:20 ` OT: using ZIP based files with git (was: How to deal with small projects which are often changing their status/ person) Karl Voit
2013-01-22 21:39 ` How to deal with small projects which are often changing their status/ person Thomas S. Dye
2013-01-22 22:27 ` M
2013-01-22 22:49 ` Thomas S. Dye [this message]
2013-01-23 1:59 ` Eric Abrahamsen
2013-01-23 9:15 ` Julian Burgos
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=m1libk6dfz.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=Elwood151@web.de \
--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).