emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Andrew Hyatt <ahyatt@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Agenda clocktable & archive issue
Date: Sun, 28 Jan 2024 14:59:59 -0400	[thread overview]
Message-ID: <m2jzntmggg.fsf@gmail.com> (raw)


I've noticed that in the agenda, the clocktable report (from the "R"
key), does not include archive files, even when I have set clocktables
to do so in my init-file:

(plist-put org-clocktable-defaults :scope 'agenda-with-archives)

First of all, I think it makes more logical sense to include archives,
since there isn't anything about archiving that means the times that the
items are worked on are no longer important for reports.

But, even if that's not the case, it should be that the user can change
this, but right now it's all hardcoded in the org-agenda-list function.
The reason it doesn't is because in org-dblock-write:clocktable, the
plists are combined with the params taking precedence, which probably
doesn't make sense. In this case, the params are the defaults, and
org-clocktable-defaults are the things I can modify, so it seems like
org-clocktable-defaults should take preference.

I'm happy to send a patch to fix this, but not sure what the best
solution here.  My guess is that the safest fix is to make another
variable for whether the report should include archives or not.  But I
suspect the best fix is to make the org-clocktable-defaults take
precedence.

Is my understanding of this correct?  Any thoughts on what should be
done here?

next             reply	other threads:[~2024-01-28 19:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28 18:59 Andrew Hyatt [this message]
2024-01-28 20:40 ` Agenda clocktable & archive issue Ihor Radchenko
2024-01-28 22:18   ` Andrew Hyatt
2024-01-28 22:34     ` Ihor Radchenko
2024-01-29  1:36       ` Andrew Hyatt
2024-01-29 13:11         ` Ihor Radchenko
2024-01-29 16:46           ` Andrew Hyatt
2024-01-29 17:00             ` 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=m2jzntmggg.fsf@gmail.com \
    --to=ahyatt@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

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