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

From: Éibhear <eibhear.geo@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Bug: Clock report failing with "invalid time specification" [9.2.1 (9.2.1-dist @ /home/eibhear/eibhear_org/lisp/org-9/lisp/)]
Date: Wed, 20 Feb 2019 17:27:26 +0000	[thread overview]
Message-ID: <ad4156b7-1dc5-0730-e341-9db0c3e35638@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1529 bytes --]

Hi,

I believe there is a bug in the preparation of a clock report when the
:step parameter is set.

Example:
========
* Headline 1
  :LOGBOOK:
  CLOCK: [2019-02-20 Wed 08:39]--[2019-02-20 Wed 14:05] =>  5:26
  CLOCK: [2019-02-19 Tue 13:38]--[2019-02-19 Tue 17:48] =>  4:10
  CLOCK: [2019-02-19 Tue 08:42]--[2019-02-19 Tue 12:40] =>  3:58
  CLOCK: [2019-02-18 Mon 15:34]--[2019-02-18 Mon 17:44] =>  2:10
  CLOCK: [2019-02-18 Mon 13:41]--[2019-02-18 Mon 14:48] =>  1:07
  CLOCK: [2019-02-18 Mon 08:32]--[2019-02-18 Mon 12:58] =>  4:26
  :END:

  Some text

  #+BEGIN: clocktable :scope file :maxlevel 2 :block thisweek :step week

  #+END:

Typing C-c C-c to refresh the table results in an error "invalid time
specification", failing on line 2738 of org-clock.el.

When I revert to org-9.2.0, the error is present, but when I revert to
org-9.1.9, the clocktable refreshes successfully.

Éibhear

Emacs  : GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5)
 of 2017-09-12 on hullmann, modified by Debian
Package: Org mode version 9.2.1 (9.2.1-dist @
/home/eibhear/eibhear_org/lisp/org-9/lisp/)

-- 
Éibhear Ó hAnluain
Dublin, Ireland.
+-------------------------------+--------------------------------+
| e-mail: eibhear.geo@gmail.com | Web: [http://www.gibiris.org/] |
| Twitter: @eibhear             | Google+: +Éibhear Ó hAnluain   |
| Mobile: +353 86 856 5666      | VoIP: sip:eibhear@linphone.org |
+-------------------------------+--------------------------------+


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

next             reply	other threads:[~2019-02-20 17:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 17:27 Éibhear [this message]
2019-02-20 21:17 ` Bug: Clock report failing with "invalid time specification" [9.2.1 (9.2.1-dist @ /home/eibhear/eibhear_org/lisp/org-9/lisp/)] 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=ad4156b7-1dc5-0730-e341-9db0c3e35638@gmail.com \
    --to=eibhear.geo@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).