From: Allen Li <vianchielfaura@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 24791@debbugs.gnu.org, "Jan Böhm" <schmuufanpost@gmx.de>
Subject: bug#24791: bug#24791: org-todo-yesterday behaves like plain org-todo (incorrect timestamp)
Date: Fri, 1 Dec 2017 20:00:11 -0800 [thread overview]
Message-ID: <CAJr1M6fXPJs92X4Y9iGzdXB3t-bDTZsHAFEfdVUznJVU-5P_9g@mail.gmail.com> (raw)
In-Reply-To: <878temdsig.fsf@nicolasgoaziou.fr>
On Fri, Dec 1, 2017 at 1:53 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Jan Böhm <schmuufanpost@gmx.de> writes:
>
>> Symptoms: both org-todo-yesterday and org-agenda-todo-yesterday behave
>> just like normally setting todo state to "DONE" with org-todo.
>> Specifically, the timestamp
>> added in the log takes the current time instead of 23:59 of the previous
>> day, as would be expected.
>>
>> Replicate behaviour:
>> start emacs -Q
>> set org-log-done to "time"
>> visit new file and switch to org mode
>> create TODO headline and set TODO state to "DONE" by calling
>> "org-todo-yesterday"
>> ⇒ todo state is set to DONE correctly, but the timestamp inserted in
>> the log drawer is the current time.
>
> I cannot reproduce it in a recent Org release. Could you double-check
> with a newer Org?
I am going to blindly wager that this is yet another bug caused by Org
mode's subtle timezone issues.
I can reproduce it (and crucially, I am not in the GMT time zone),
although the repro recipe produces a CLOSED timestamp and not a log
drawer timestamp.
next prev parent reply other threads:[~2017-12-02 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <609c94f4-8b0f-02b7-d467-3651c3c3fe59@gmx.de>
2017-12-01 21:53 ` bug#24791: org-todo-yesterday behaves like plain org-todo (incorrect timestamp) Nicolas Goaziou
2017-12-02 4:00 ` Allen Li [this message]
2017-12-04 19:59 ` bug#24791: " Nicolas Goaziou
2017-12-04 20:12 ` Jan Böhm
2017-12-08 0:51 ` Allen Li
2017-12-29 11:44 ` 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=CAJr1M6fXPJs92X4Y9iGzdXB3t-bDTZsHAFEfdVUznJVU-5P_9g@mail.gmail.com \
--to=vianchielfaura@gmail.com \
--cc=24791@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=schmuufanpost@gmx.de \
/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).