emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: [QUESTION] How to generate org-agenda view for clocked tasks and logs etc which are sorted by timestamps?
Date: Thu, 4 Nov 2021 16:03:34 +0100	[thread overview]
Message-ID: <YYP2RohxGRX+MpPS@maokai> (raw)
In-Reply-To: <CAL1eYu+ew8BqRSRPyF5078FYr1yx+zVM3X8SCfkX_D4Gkp7cXQ@mail.gmail.com>

On Thu, Nov 04, 2021 at 12:16:19PM +0800, stardiviner wrote:
> How to use elisp code to generate an org-agenda view for clocked tasks and
> logs etc which are sorted by timestamps? I want to view my daily done tasks
> and attach them as part of diary (maybe use org source block elisp code to
> generate output?)
> So how to setup `org-agenda-custom-commands` to archive this purpose?

I routinely export my agenda to HTML with logbook mode enabled and
inactive timestamps. This shows a complete timeline of my actions.  I
save timestamps on changing TODO to DONE, use active timestamps for
appointments, and I constantly add inactive timestamps while taking
notes. I use this to justify billing to clients.

I open the agenda, v m to make a monthly view, L for logbook, ] to
enable inactive timestamps, and then C-x C-w to save. You may be able
to just use elisp to trigger these actions.

I don't do it often enough to automate it. I love being able to
flatten my tree of notes into a timeline this way.

Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

  reply	other threads:[~2021-11-04 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  4:16 [QUESTION] How to generate org-agenda view for clocked tasks and logs etc which are sorted by timestamps? stardiviner
2021-11-04 15:03 ` Russell Adams [this message]
2021-11-05 11:20   ` Christopher M. Miles
2021-11-05 11:53     ` Ihor Radchenko
2021-11-05 14:36       ` [SOLVED] " Christopher M. Miles

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=YYP2RohxGRX+MpPS@maokai \
    --to=rladams@adamsinfoserv.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).