From: Julian Bean <jules@jellybean.co.uk>
To: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
Cc: emacs-orgmode@gnu.org
Subject: Re: Error message could be improved - Specified time is not representable
Date: Tue, 24 May 2011 09:31:58 +0100 [thread overview]
Message-ID: <DD8E7A36-4C57-4F71-A0CD-07FFEF0D9138@jellybean.co.uk> (raw)
In-Reply-To: <83k4dg7bul.fsf@yahoo.it>
On 24 May 2011, at 09:16, Giovanni Ridolfi wrote:
> Julian Bean <jules@jellybean.co.uk> writes:
>
>>
>> [...] I tracked this down to an erroneous SCHEDULED date of 1st
>> January 1904 buried inside a task. [...]
>>
>> Evidently, for some reason, calling (encode-time 0 0 0 1 1 1904) on
>> 23.3 causes the error above,
>
> " This is probably related to the same problem as discussed in this
> thread:
> http://thread.gmane.org/gmane.emacs.orgmode/39206
>
> 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.
>
>> whereas on 23.1 it's silently ignored?
>
> Since it is an Emacs problem I think you should ask Emacs's
> developers:
> emacs-devel@gnu.org
>
> or file a bug report:
> 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
prev parent reply other threads:[~2011-05-24 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 7:06 Error message could be improved - Specified time is not representable Julian Bean
2011-05-24 8:16 ` Giovanni Ridolfi
2011-05-24 8:31 ` Julian Bean [this message]
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=DD8E7A36-4C57-4F71-A0CD-07FFEF0D9138@jellybean.co.uk \
--to=jules@jellybean.co.uk \
--cc=emacs-orgmode@gnu.org \
--cc=giovanni.ridolfi@yahoo.it \
/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).