From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marco Wahl <marcowahlsoft@gmail.com>
Subject: Re: is this a known issue in clocktable output?
Date: Sat, 30 Nov 2019 10:05:51 +0100
Message-ID: <84sgm5sphs.fsf@gmail.com>
References: <CALHmx3jLa1C+D84_mbgWADwjT4vBP9HMJpaRFoo9JbMWX0GJBw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:60526)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1iayhX-0005Xw-Dv
 for emacs-orgmode@gnu.org; Sat, 30 Nov 2019 04:06:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1iayhW-0006MN-9h
 for emacs-orgmode@gnu.org; Sat, 30 Nov 2019 04:06:03 -0500
Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:51284
 helo=blaine.gmane.org)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <geo-emacs-orgmode@m.gmane.org>)
 id 1iayhW-0006HN-2D
 for emacs-orgmode@gnu.org; Sat, 30 Nov 2019 04:06:02 -0500
Received: from list by blaine.gmane.org with local (Exim 4.89)
 (envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1iayhS-000p0A-R3
 for emacs-orgmode@gnu.org; Sat, 30 Nov 2019 10:05:58 +0100
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
 <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: emacs-orgmode@gnu.org

Soubzriquet <soubzriquet@gmail.com> writes:

> I'm new to using org-mode for time tracking, and have run into an odd issue
> with using "day" steps where the date is getting offset sometimes.
>
> I saw the issue with 26.1, was not fixed by updating  to current
> environment with an empty init.el on OS X:

[...]

> * Day 1
>   :LOGBOOK:
>   CLOCK: [2019-11-01 Fri 10:00]--[2019-11-01 Fri 11:00] =>  1:00
>   :END:
> * Day 2
>   :LOGBOOK:
>   CLOCK: [2019-11-02 Sat 10:00]--[2019-11-02 Sat 12:00] =>  2:00
>   :END:
> * Day 3
>   :LOGBOOK:
>   CLOCK: [2019-11-03 Sun 10:00]--[2019-11-03 Sun 13:00] =>  3:00
>   :END:
> * Day 4
>   :LOGBOOK:
>   CLOCK: [2019-11-04 Mon 10:00]--[2019-11-04 Mon 14:00] =>  4:00
>   :END:
> * Day 5
>   :LOGBOOK:
>   CLOCK: [2019-11-05 Tue 10:00]--[2019-11-05 Tue 15:00] =>  5:00
>   :END:
> * Day 6
>   :LOGBOOK:
>   CLOCK: [2019-11-06 Wed 10:00]--[2019-11-06 Wed 16:00] =>  6:00
>   :END:
>
> #+BEGIN: clocktable :scope file :maxlevel 2 :block thismonth :step day :stepskip0 t
>
> Daily report: [2019-11-01 Fri]
> | Headline     | Time   |
> |--------------+--------|
> | *Total time* | *1:00* |
> |--------------+--------|
> | Day 1        | 1:00   |
>
> Daily report: [2019-11-02 Sat]
> | Headline     | Time   |
> |--------------+--------|
> | *Total time* | *2:00* |
> |--------------+--------|
> | Day 2        | 2:00   |
>
> Daily report: [2019-11-03 Sun]
> | Headline     | Time   |
> |--------------+--------|
> | *Total time* | *3:00* |
> |--------------+--------|
> | Day 3        | 3:00   |
>
> Daily report: [2019-11-03 Sun]
> | Headline     | Time   |
> |--------------+--------|
> | *Total time* | *4:00* |
> |--------------+--------|
> | Day 4        | 4:00   |
>
> Daily report: [2019-11-04 Mon]
> | Headline     | Time   |
> |--------------+--------|
> | *Total time* | *5:00* |
> |--------------+--------|
> | Day 5        | 5:00   |
>
> Daily report: [2019-11-05 Tue]
> | Headline     | Time   |
> |--------------+--------|
> | *Total time* | *6:00* |
> |--------------+--------|
> | Day 6        | 6:00   |
>
> #+END:

I can not reproduce this behavior.

Could you please check again with emacs -Q?


Thanks.