emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: emacs-orgmode@gnu.org
Subject: Re: Tips on maintaining history in Org Mode
Date: Fri, 26 Feb 2021 14:24:14 -0500	[thread overview]
Message-ID: <45e4dc6434becb1552adc7df544db01a@isnotmyreal.name> (raw)
In-Reply-To: <SJ0PR03MB5455949D9325AC0CF3FEC64F9B9D9@SJ0PR03MB5455.namprd03.prod.outlook.com>

On 2021-02-26 01:22, David Masterson wrote:
> 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.
> 
> Suggestions

I agree with what others already said about logging state changes with
timestamps.  I do the same and find this an extremely handy place to
put "metadata about the task, or reason that it changed" and keep it
separate/hidden from the main body of the task (which in my mind
should only contain info about the subject of the headline / task
itself).

However when you say "history" I suspect you mean "archive" and this
is something I have been thinking about a long time as well.  Because
I think the current way that Orgmode handles this is a bit naive /
simplistic.  Well, at least there is the option to create your own
archival function, which I suspect I will do at some point.  In fact I
have been thinking about the best way to do that for some time
already.

Cheers,
TRS-80


  parent reply	other threads:[~2021-02-26 19:25 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
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 [this message]
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

  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=45e4dc6434becb1552adc7df544db01a@isnotmyreal.name \
    --to=lists.trs-80@isnotmyreal.name \
    --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).