emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Masterson <dsmasterson92630@outlook.com>
To: emacs-orgmode@gnu.org
Subject: Re: Tips on maintaining history in Org Mode
Date: Fri, 26 Feb 2021 15:00:02 -0800	[thread overview]
Message-ID: <SJ0PR03MB54554F09F1784A4DE894233D9B9D9@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87sg5jdva4.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 26 Feb 2021 09:37:39 +0000")

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> My approach is simple.  For TODO items, I archive to separate file when
> done.  That file is easily searchable, e.g. using C-c /.

Ah! org-occur! That's something forgot about and looks useful.

> I keep both the original file and the archive file under revision
> control, just in case.

I do that, too.

>> The issue (I think) is, when you mark the TODO as DONE, you lose the
>> info of what the TODO was originally.
>
> What info is lost?  In fact, if you log state changes, all the
> information is there.

I see how that workss now with org-occur.

> By the way, if you have recurring items, one package that you might find
> useful is org-recur which is on ELPA.

Thanks

-- 
David Masterson


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

  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=SJ0PR03MB54554F09F1784A4DE894233D9B9D9@SJ0PR03MB5455.namprd03.prod.outlook.com \
    --to=dsmasterson92630@outlook.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 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).