From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: is this a known issue in clocktable output?
Date: Mon, 02 Dec 2019 15:04:59 -0500 [thread overview]
Message-ID: <875ziybij8.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 84a78c2o94.fsf@gmail.com
Marco Wahl <marcowahlsoft@gmail.com> writes:
> Soubzriquet <soubzriquet@gmail.com> writes:
>>> [...]
>
>>> > 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:
>>> > ...
>>> > 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 |
>>> >
>>> I can not reproduce this behavior.
>
>> Hi, sorry I was not more clear - the issue occurs also with emacs -Q or
>> with empty init.el on my system.
>
> Okay, thanks. I think I'm at the end of my abilities to investigate the
> issue further.
>
> I suggest you dig a little deeper for better understanding. E.g.:
>
> - Try make the example of failure as small as you can.
>
> - Check with a newer version of Org.
>
> - Debug the issue.
>
>
> Possibly someone else can confirm the issue.
>
>
I can reproduce the issue with 9.1.9, but it goes away with 9.2 or later.
Marco's suggestion to use a newer version is the right thing to do.
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
prev parent reply other threads:[~2019-12-02 20:05 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
2019-11-30 19:50 ` Soubzriquet
2019-12-01 13:01 ` Marco Wahl
2019-12-02 20:04 ` Nick Dokos [this message]
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=875ziybij8.fsf@alphaville.usersys.redhat.com \
--to=ndokos@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).