From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Tips on maintaining history in Org Mode
Date: Fri, 26 Feb 2021 18:54:17 +1100 [thread overview]
Message-ID: <87zgzr9s7f.fsf@gmail.com> (raw)
In-Reply-To: <SJ0PR03MB5455949D9325AC0CF3FEC64F9B9D9@SJ0PR03MB5455.namprd03.prod.outlook.com>
David Masterson <dsmasterson92630@outlook.com> 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.
For non-TODO items, I will often put an inactive timestamp in the
heading title.
I also make extensive use of the ability to add timestamp entries as
part of capture templates - for exmaple, my notes and even the file of
bookmakrs (RUIs) I have.
--
Tim Cross
next prev parent reply other threads:[~2021-02-26 7:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 6:22 Tips on maintaining history in Org Mode 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 [this message]
2021-02-26 22:55 ` David Masterson
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgzr9s7f.fsf@gmail.com \
--to=theophilusx@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.