From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julian Bean Subject: Error message could be improved - Specified time is not representable Date: Tue, 24 May 2011 08:06:19 +0100 Message-ID: <2D8D6FEC-69C7-43CF-B755-BB7BC49977AA@jellybean.co.uk> 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]:47686) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QOlmZ-0002B9-M2 for emacs-orgmode@gnu.org; Tue, 24 May 2011 03:12:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QOlmY-0005jG-Pz for emacs-orgmode@gnu.org; Tue, 24 May 2011 03:11:59 -0400 Received: from roobarb.crazydogs.org ([93.93.128.87]:57492 helo=roobarb.jellybean.co.uk) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QOlmY-0005ip-Ln for emacs-orgmode@gnu.org; Tue, 24 May 2011 03:11:58 -0400 Received: from [89.193.255.177] (helo=[192.168.1.115]) by roobarb.jellybean.co.uk with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1QOlmJ-00047a-Va for emacs-orgmode@gnu.org; Tue, 24 May 2011 08:11:46 +0100 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: emacs-orgmode@gnu.org Hi all, On upgrading to emacs 23.3 (from emacs 23.1) my daily/weekly agenda = became unusable, giving the error message "Specified time is not = representable". After a bit of poking around in the backtrace I tracked this down to an = erroneous SCHEDULED date of 1st January 1904 buried inside a task. (This = date was created by a bug in a script I was using to import TODOs from = another system). Evidently, for some reason, calling (encode-time 0 0 0 1 1 1904) on 23.3 = causes the error above, whereas on 23.1 it's silently ignored? I think the best thing for org-mode is to catch this error and report it = to the user in a more understandable way so they can locate and fix the = buggy timestamp - at least, include the full text of the timestamp so = they can easily grep for it? Jules