From: David Masterson <firstname.lastname@example.org>
To: Tim Cross <email@example.com>
Subject: Re: Tips on maintaining history in Org Mode
Date: Fri, 26 Feb 2021 14:55:16 -0800 [thread overview]
Message-ID: <SJ0PR03MB5455A0B7779A6D32EDB6EC099B9D9@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Tim Cross's message of "Fri, 26 Feb 2021 18:54:17 +1100")
Tim Cross <email@example.com> writes:
> David Masterson <firstname.lastname@example.org> writes:
>> There are many ways of maintaining history in a group of Org files:
>> 1. Archive within a file
>> 2. Archive to a separate (archive) file
>> 3. Special TODO types for history
>> 4. Special TAG types for history
>> 5. etc.
>> My question is, if you have meetings/phone calls as TODOs, what is the
>> preferred way to handle when they move into history so that, *much*
>> later, you can easily produce a list of all of the meetings/phone calls
>> with dates and times of them? The issue (I think) is, when you mark the
>> TODO as DONE, you lose the info of what the TODO was originally.
> A lot will depend on your requirements.
> For me, my TODOs are setup so that they record a date stamp for when
> they were added and whenever they change state e.g. started, done,
> delegated etc.
So, you use progress logging.
> For non-TODO items, I will often put an inactive timestamp in the
> heading title.
Do your headings become busy?
What would you use to then make a list of all meetings you had last year?
next prev parent reply other threads:[~2021-02-26 22:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 6:22 David Masterson
2021-02-26 7:25 ` Ihor Radchenko
2021-02-26 22:51 ` David Masterson
2021-02-27 6:28 ` Ihor Radchenko
2021-03-01 5:45 ` David Masterson
2021-02-26 7:54 ` Tim Cross
2021-02-26 22:55 ` David Masterson [this message]
2021-02-26 22:59 ` Tim Cross
2021-02-27 3:17 ` David Masterson
2021-02-27 4:21 ` Samuel Wales
2021-02-27 6:38 ` Ihor Radchenko
2021-02-26 9:37 ` Eric S Fraga
2021-02-26 23:00 ` David Masterson
2021-02-26 19:24 ` TRS-80
2021-02-26 21:34 ` Samuel Wales
2021-02-27 6:42 ` Ihor Radchenko
2021-02-28 22:13 ` Samuel Wales
2021-03-01 3:42 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).