From: umberto boccioni <vexware@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug? org-clock-report options order sensitive? [9.1.2 (9.1.2-25-g2567fe-elpa @ emacs/.emacs.d/elpa/org-20171030/)]
Date: Wed, 1 Nov 2017 17:36:00 +1000 [thread overview]
Message-ID: <CALVmW4==iwYnaLd4xCCAQ3vZMgX3c=JbK_C8UFiT4ZYKuwZ5Xw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]
Emacs : GNU Emacs 25.2.1 (x86_64-w64-mingw32)
of 2017-04-25
Package: Org mode version 9.1.2 (9.1.2-25-g2567fe-elpa @ emacs/.
emacs.d/elpa/org-20171030/)
In a .org file (not an agenda buffer) using the clock-report (M-x
org-clock-report) with otherwise default options, the order of options
manually entered seems to change the output of the report. Is this a
config thing on my end, or is this intended and I overlooked the relevant
section in the manual?
Below are the outputs of org-clock-report with only two options reversed
(not sure if tables will come out aligned, but differences are obvious).
With ":fileskip0" option last, the output is as expected, with the ":scope
agenda" using all agenda files as sources for the clocks, and fileskip
paring away tables from files not used.
However, with the "fileskip0" option first, the "scope" option is not
honored and only the clock from the current buffer (the default choice for
clocktable) is shown. To do this, I manually reversed the options and then
updated the dynamic block via (M-x org-dblock-update) with cursor on the
"BEGIN" line. I get similar behavior with other options, e.g. ":link" Is
anyone able to reproduce this?
#+BEGIN: clocktable :scope agenda :fileskip0
#+CAPTION: Clock summary at [2017-11-01 Wed 16:09]
| File | Headline | Time
| |
|-------------------+---------------------------------------
+------------+------|
| | ALL *Total time* | *1d 16:50*
| |
|-------------------+---------------------------------------
+------------+------|
| WorkTasks.org | *File time* | *1d 0:25*
| |
| | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx... | 1d 0:25
| |
|-------------------+---------------------------------------
+------------+------|
| Notesxxxxxxxx.org | *File time* | *7:14*
| |
| | xxxxxxxx | 7:14
| |
|-------------------+---------------------------------------
+------------+------|
| todo.org | *File time* | *9:11*
| |
| | xxxxxxxxxxxxxxxxxxxxxxs | 0:19
| |
| | xxxxxxxxxxxxxx | 8:52
| |
| | \_ sign xxxxx | |
8:52 |
#+END:
#+BEGIN: clocktable :fileskip0 :scope agenda
#+CAPTION: Clock summary at [2017-11-01 Wed 16:52]
| Headline | Time |
|--------------+--------|
| *Total time* | *7:14* |
|--------------+--------|
| xxxxxxxx | 7:14 |
#+END:
[-- Attachment #2: Type: text/html, Size: 3568 bytes --]
next reply other threads:[~2017-11-01 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 7:36 umberto boccioni [this message]
2017-11-08 14:14 ` Bug? org-clock-report options order sensitive? [9.1.2 (9.1.2-25-g2567fe-elpa @ emacs/.emacs.d/elpa/org-20171030/)] 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='CALVmW4==iwYnaLd4xCCAQ3vZMgX3c=JbK_C8UFiT4ZYKuwZ5Xw@mail.gmail.com' \
--to=vexware@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
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).