From: Bernt Hansen <bernt@norang.ca>
To: Geert Kloosterman <g.j.kloosterman@gmail.com>,
John Wiegley <johnw@newartisans.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: org-todo-yesterday logs wrong date
Date: Tue, 08 Nov 2011 21:22:42 -0500 [thread overview]
Message-ID: <877h3af30t.fsf@norang.ca> (raw)
In-Reply-To: <CAE1ac0koF_OvaGnEghq2S7nm8ttZU4yo0wAeUOBj_Fmj14Be4w@mail.gmail.com> (Geert Kloosterman's message of "Mon, 7 Nov 2011 12:29:27 +0100")
Geert Kloosterman <g.j.kloosterman@gmail.com> writes:
> Hi all,
>
> On Wed, Oct 19, 2011 at 1:17 AM, Viktor Rosenfeld <
> listuser36@googlemail.com> wrote:
>
>
> org-todo-yesterday and org-agenda-todo-yesterday log a note using
> the
> current timestamp and not a timestamp of 23:59 of yesterday's
> date.
>
> I'm using Org-Mode 7.7 pulled today from the git repository.
>
>
>
> I'm experiencing the same problem with the org-mode version I pulled
> from git today.
>
> Switching back to the 7.7 tarball fixes the problem.
>
> Best regards,
> Geert Kloosterman
>
Git bisect identifies the following commit as the source of this
problem.
7d2d8f884b2e22e3056553ea68858fe4fc674427 is the first bad commit
commit 7d2d8f884b2e22e3056553ea68858fe4fc674427
Author: John Wiegley <johnw@newartisans.com>
Date: Sat Aug 13 03:21:49 2011 -0500
Add customization variable `org-use-effective-time'
If non-nil, consider `org-extend-today-until' when creating timestamps.
For example, if `org-extend-today-until' is 8, and it's 4am, then the
"effective time" of any timestamps between midnight and 8am will be
23:59 of the previous day.
:040000 040000 a33f65040163763ed06996b9ffc18bcfc5884457 0782571b08e0a128fa3b072b8b8edf177c001ca3 M lisp
Regards,
Bernt
next prev parent reply other threads:[~2011-11-09 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 23:17 BUG: org-todo-yesterday logs wrong date Viktor Rosenfeld
2011-11-07 11:29 ` Geert Kloosterman
2011-11-09 2:22 ` Bernt Hansen [this message]
2011-11-11 23:55 ` Viktor Rosenfeld
2012-04-03 7:58 ` Bastien
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=877h3af30t.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=g.j.kloosterman@gmail.com \
--cc=johnw@newartisans.com \
/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).