emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeff Trull <edaskel@att.net>
To: emacs-orgmode@gnu.org
Subject: Re: erroneous clocktable for November 2018 - possible DST problem
Date: Sat, 17 Nov 2018 23:22:37 -0800	[thread overview]
Message-ID: <CAF_DUeFDhvTgOp6qNs-1FMP7ZA-5RDuSD42C2NcVRXvsChdOCw@mail.gmail.com> (raw)
In-Reply-To: <87bm6nfmxu.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

OK, I can confirm that the 20181112 release has this problem but the
development version from github does not.

Thanks,
Jeff


On Sat, Nov 17, 2018 at 12:50 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Jeff Trull <edaskel@att.net> writes:
>
> > Clocktables containing work in November of 2018 are reported incorrectly,
> > showing the wrong day (typically one earlier than the correct date). For
> > example, in the attached repro.org, work is performed on the 3rd and
> 5th of
> > November, but when daily reports are used in the clocktable the work on 5
> > November is reported as occurring on 4 November. Reporting 1-4 November
> and
> > 5-30 November separately works around the problem.
> >
> > In the US, Daylight Savings ended on 4 November; this fact plus a
> previous
> > problem (reported here:
> >
> https://stackoverflow.com/questions/42821604/why-is-emacs-org-mode-missing-one-date-from-clocktable
> )
> > suggests DST is involved.
>
> I think something like this was fixed in development branch. Please test
> it if you can.
>
> Regards,
>
> --
> Nicolas Goaziou
>

[-- Attachment #2: Type: text/html, Size: 1757 bytes --]

      reply	other threads:[~2018-11-18  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-17  8:06 erroneous clocktable for November 2018 - possible DST problem Jeff Trull
2018-11-17 20:50 ` Nicolas Goaziou
2018-11-18  7:22   ` Jeff Trull [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=CAF_DUeFDhvTgOp6qNs-1FMP7ZA-5RDuSD42C2NcVRXvsChdOCw@mail.gmail.com \
    --to=edaskel@att.net \
    --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).