From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julian Bean Subject: Re: Error message could be improved - Specified time is not representable Date: Tue, 24 May 2011 09:31:58 +0100 Message-ID: References: <2D8D6FEC-69C7-43CF-B755-BB7BC49977AA@jellybean.co.uk> <83k4dg7bul.fsf@yahoo.it> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:54814) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QOn2W-0003W8-AT for emacs-orgmode@gnu.org; Tue, 24 May 2011 04:32:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QOn2P-0001gm-NM for emacs-orgmode@gnu.org; Tue, 24 May 2011 04:32:32 -0400 Received: from roobarb.crazydogs.org ([93.93.128.87]:60340 helo=roobarb.jellybean.co.uk) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QOn2P-0001gM-HE for emacs-orgmode@gnu.org; Tue, 24 May 2011 04:32:25 -0400 In-Reply-To: <83k4dg7bul.fsf@yahoo.it> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Giovanni Ridolfi Cc: emacs-orgmode@gnu.org On 24 May 2011, at 09:16, Giovanni Ridolfi wrote: > Julian Bean writes: >=20 >>=20 >> [...] I tracked this down to an erroneous SCHEDULED date of 1st >> January 1904 buried inside a task. [...] >>=20 >> Evidently, for some reason, calling (encode-time 0 0 0 1 1 1904) on >> 23.3 causes the error above,=20 >=20 > " This is probably related to the same problem as discussed in this > thread: > http://thread.gmane.org/gmane.emacs.orgmode/39206 >=20 > on the limitations of unix time (whether on Unix or not...)." Thanks, I missed that. You're right, that describes another = manifestation of the same issue. >=20 >> whereas on 23.1 it's silently ignored? >=20 > Since it is an Emacs problem I think you should ask Emacs's=20 > developers: > emacs-devel@gnu.org=20 >=20 > or file a bug report:=20 > M-x report-emacs-bug or write to > bug-gnu-emacs@gnu.org I disagree. It's not a clear emacs bug - the docstring for encode-time = says very clearly "Years before 1970 are not guaranteed to work. On = some systems, year values as low as 1901 do work.". encode-time is = working as documented and I certainly don't understand emacs' date-time = internals well enough to suggest a better way. The *org-mode* bug is, simply, the error message (hence my message = title). If this exception does occur, it would be nice if org-mode would = catch it, and provide better information to the user about which = timestamp he needs to fix. Jules