emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: David Masterson <dsmasterson92630@outlook.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Tips on maintaining history in Org Mode
Date: Sat, 27 Feb 2021 14:28:13 +0800	[thread overview]
Message-ID: <87czwmc9du.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB5455FD17CD8FA3853983D5509B9D9@SJ0PR03MB5455.namprd03.prod.outlook.com>

David Masterson <dsmasterson92630@outlook.com> writes:

> Interesting, but then how do you get the list?  I mean is there an
> agenda to use?

Generally yes, you can use agenda. Or you can use sparse tree (more manual).
For agenda, if you customise org-log-done, you can use
org-agenda-log-mode ("v l" or "v L" in an agenda buffer). You can add
archived items as well with "v a" or/and "v A".

Just org-agenda-log-mode will show everything, not just calls. Narrowing
to calls only will depend on how you define a todo, which is a call.

If you use something like PHONE or CALL todo keywords, it might be
slightly tricky. You will need to customise org-todo-keywords, so that
your CALL->DONE changes are recorded (see the org-todo-keywords
docstring). You will also need to filter displayed items in agenda by
regexp involving the keyword you use to define the call.

An easier way could be marking your calls with a tag. Then, you can
filter your org-agenda-log by that tag to show only calls.

Hope it helps.


  reply	other threads:[~2021-02-27  6:24 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 [this message]
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
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:

  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=87czwmc9du.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=dsmasterson92630@outlook.com \
    --cc=emacs-orgmode@gnu.org \


* 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).