emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Clocktable parameters
Date: Sun, 03 Jul 2022 08:05:05 +0100	[thread overview]
Message-ID: <87a69qwuam.fsf@yandex.com> (raw)
In-Reply-To: <878rpchyva.fsf@localhost> (Ihor Radchenko's message of "Sat, 02 Jul 2022 13:23:05 +0800")

>>>>> Ihor Radchenko <yantar92@gmail.com> writes:

    > Colin Baxter 😺️ <m43cap@yandex.com> writes:
    >> I find the differences between the variables
    >> 
    >> (1) org-clocktable-defaults (2)
    >> org-agenda-clockreport-parameter-plist
    >> 
    >> hard to understand.
    >> 
    >> Ok, (1) seems reasonably clear. It's described in `info' (there's
    >> no doc-string). The variable (2) confuses me. According to its
    >> doc string (there's no `info' mention) it gives parameters for a
    >> clock table in the daily and weekly agendas. How is that
    >> different from (1)?
    >> 
    >> Am I correct in thinking (1) is primarily for a clock table not
    >> associated with the agenda? Quite how such a clocktable would
    >> arise is unclear to me.

    > 8.4.2 The clock table section of the manual described the
    > clocktables you can create inside Org
    > buffers. org-clocktable-defaults apply for those clocktables.

    > org-agenda-clockreport-parameter-plist only applies to
    > org-agenda-clockreport-mode inside agenda
    > views. org-clocktable-defaults is disregarded inside Org agendas.

Thank you very much for this explanation.

Best wishes,


      reply	other threads:[~2022-07-03  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 11:12 Clocktable parameters Colin Baxter 😺
2022-07-02  5:23 ` Ihor Radchenko
2022-07-03  7:05   ` Colin Baxter [this message]

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=87a69qwuam.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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).