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

From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: is this a known issue in clocktable output?
Date: Sat, 30 Nov 2019 10:05:51 +0100	[thread overview]
Message-ID: <84sgm5sphs.fsf@gmail.com> (raw)
In-Reply-To: CALHmx3jLa1C+D84_mbgWADwjT4vBP9HMJpaRFoo9JbMWX0GJBw@mail.gmail.com

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.

next prev parent reply	other threads:[~2019-11-30  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  0:42 is this a known issue in clocktable output? Soubzriquet
2019-11-30  9:05 ` Marco Wahl [this message]
2019-11-30 19:50   ` Soubzriquet
2019-12-01 13:01     ` Marco Wahl
2019-12-02 20:04       ` Nick Dokos

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=84sgm5sphs.fsf@gmail.com \
    --to=marcowahlsoft@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).