GNU bug report logs - #23299
25.1.50; org-timestamp-change: Invalid time zone specification: (nil nil nil)

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23299 in the body.
You can then email your comments to 23299 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Peter Münster <pmlists <at> free.fr>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.1.50;
 org-timestamp-change: Invalid time zone specification: (nil nil nil)
Date: Sat, 16 Apr 2016 11:08:30 +0200

Hi,

With latest git-emacs, I get this error, after org-timestamp-up-day on a
time-stamp:

org-timestamp-change: Invalid time zone specification: (nil nil nil)

How could I make org-timestamp-up-day work again please?

TIA for any help,
-- 
           Peter

Message #8 received at 23299 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Peter Münster <pmlists <at> free.fr>
Cc: 23299 <at> debbugs.gnu.org
Subject: Re: bug#23299: 25.1.50;
 org-timestamp-change: Invalid time zone specification: (nil nil nil)
Date: Sat, 16 Apr 2016 13:57:41 +0300

> From: Peter Münster <pmlists <at> free.fr>
> Date: Sat, 16 Apr 2016 11:08:30 +0200
> 
> With latest git-emacs, I get this error, after org-timestamp-up-day on a
> time-stamp:
> 
> org-timestamp-change: Invalid time zone specification: (nil nil nil)
> 
> How could I make org-timestamp-up-day work again please?

Please show a complete recipe for reproducing this problem, starting
with "emacs -Q".  (I tried something simple and probably stupid, but
couldn't reproduce this.)

Thanks.

Message #11 received at 23299 <at> debbugs.gnu.org (full text, mbox):

From: Peter Münster <pmlists <at> free.fr>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 23299 <at> debbugs.gnu.org
Subject: Re: bug#23299: 25.1.50;
 org-timestamp-change: Invalid time zone specification: (nil nil nil)
Date: Sat, 16 Apr 2016 13:39:09 +0200

On Sat, Apr 16 2016, Eli Zaretskii wrote:

> Please show a complete recipe for reproducing this problem, starting
> with "emacs -Q".

- emacs -Q
- open /tmp/foo.org
- M-x org-mode
- M-S-return (org-insert-todo-heading)
- C-c C-d (org-deadline)
- go to the time-stamp
- M-x org-timestamp-up-day

-- 
           Peter

Message #14 received at 23299 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Peter Münster <pmlists <at> free.fr>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 23299 <at> debbugs.gnu.org
Subject: Re: bug#23299: 25.1.50;
 org-timestamp-change: Invalid time zone specification: (nil nil nil)
Date: Sat, 16 Apr 2016 14:20:14 +0200

Peter Münster <pmlists <at> free.fr> writes:

> - emacs -Q
> - open /tmp/foo.org
> - M-x org-mode
> - M-S-return (org-insert-todo-heading)
> - C-c C-d (org-deadline)
> - go to the time-stamp
> - M-x org-timestamp-up-day

I saw that, too.

And I got a similar error after hitting t d in the agenda (aka "mark as
done").  After the error happened, the according entry in the todo file
was broken...not good.

Michael.

Message #17 received at 23299 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Peter Münster <pmlists <at> free.fr>
Cc: 23299 <at> debbugs.gnu.org
Subject: Re: bug#23299: 25.1.50;
 org-timestamp-change: Invalid time zone specification: (nil nil nil)
Date: Sat, 16 Apr 2016 15:31:40 +0300

> From: Peter Münster <pmlists <at> free.fr>
> Cc: 23299 <at> debbugs.gnu.org
> Date: Sat, 16 Apr 2016 13:39:09 +0200
> 
> On Sat, Apr 16 2016, Eli Zaretskii wrote:
> 
> > Please show a complete recipe for reproducing this problem, starting
> > with "emacs -Q".
> 
> - emacs -Q
> - open /tmp/foo.org
> - M-x org-mode
> - M-S-return (org-insert-todo-heading)
> - C-c C-d (org-deadline)
> - go to the time-stamp
> - M-x org-timestamp-up-day

Thanks.  With this recipe, the problem happens on master, but not on
the emacs-25 branch.  This is because encode-time on master no longer
accepts a list of (nil nil nil) as a valid time-zone specification.
That list looks wrong to me, so it sounds like a bug in Org that was
exposed by the recent changes in encode-time.

Message #22 received at 23299-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Peter Münster <pmlists <at> free.fr>
Cc: 23299-done <at> debbugs.gnu.org,
 Cédric Chépied <cedric.chepied <at> gmail.com>
Subject: 25.1.50; org-timestamp-change: Invalid time zone specification: (nil
 nil nil)
Date: Wed, 20 Apr 2016 00:11:15 -0700

[Message part 1 (text/plain, inline)]

Thanks for reporting the problem. As Eli suggested, it was a typo in org.el that 
was exposed by recent changes to encode-time. I installed into master the 
attached patch, which I think fixes the bug.

[0001-Fix-org-timestamp-change-typo.txt (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.