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

From: Tyler Smith <tyler@plantarum.ca>
To: Emacs Org-Mode Help <emacs-orgmode@gnu.org>
Subject: org-clock-report overrides default :scope argument
Date: Tue, 13 Feb 2018 11:47:00 -0500	[thread overview]
Message-ID: <1518540420.4161236.1269501784.0144713F@webmail.messagingengine.com> (raw)

Hi,

I have set org-clock-clocktable-default-properties to:

    (:scope agenda :stepskip0 t :fileskip0 t :compact t :block today)

However, if I'm in a subtree and I try to insert a new clock table via ~C-c C-x C-r~ / ~org-clock-report~, org sets the options to ~:scope subtree~, ignoring my customiztion.  

This appears to be by design. However, it's unexpected, as there's nothing in the org manual to indicate that the ~:scope~ option is treated differently than the others with respect to customization. It might be nicer to users to give their preferred options a higher priority than the automatically generated ones, i.e., change

    (org-create-dblock
           (org-combine-plists org-clock-clocktable-default-properties props))

to

    (org-create-dblock
           (org-combine-plists props org-clock-clocktable-default-properties))

In the body of ~org-clock-report~. Alternatively, perhaps the org-info manual and/or the documentation for ~org-clock-clocktable-default-properties~ could be updated to indicate that a custom ~:scope~ setting will be ignored when invoked from a subtree?

Best,

Tyler 

Org mode version 9.1.6 (9.1.6-44-ge6f891-elpaplus
GNU Emacs 26.0.90 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.24) of 2017-12-21



-- 
plantarum.ca

next             reply	other threads:[~2018-02-13 16:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 16:47 Tyler Smith [this message]
2018-02-14 17:01 ` org-clock-report overrides default :scope argument Nicolas Goaziou

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=1518540420.4161236.1269501784.0144713F@webmail.messagingengine.com \
    --to=tyler@plantarum.ca \
    --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).