unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "A.C." <achirvasub@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,Colin Baxter <m43cap@yandex.com>
Cc: 37974@debbugs.gnu.org
Subject: bug#37974: eww produces "error in process filter: Specified time is not representable"
Date: Thu, 31 Oct 2019 14:50:17 -0400	[thread overview]
Message-ID: <88F94981-2880-4ADE-A25D-800675800BA4@gmail.com> (raw)
In-Reply-To: <87v9s6wl8e.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

But this resolves the 32-bit issue only, correct?

I did end up compiling the latest version (27.0.50, as reported by 'emacs --version') cloned from

git://git.savannah.gnu.org/emacs.git

on a 64-bit system and

(format-time-string "%a %b %d %H:%M:%S %Y GMT" 67768036191676800 t)

still chokes with the "Specified time is not representable" error. As before, the same expression evaluates fine to 

"Wed Dec 31 23:59:59 2147485547 GMT"

with the smaller number 

67768036191676799 = 67768036191676800 - 1





On October 30, 2019 7:01:21 AM EDT, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>Colin Baxter <m43cap@yandex.com> writes:
>
>> If it helps, I see no problem on the latest pull of emacs-27. I'm on
>> Linux 3.16.0-10-686-pae #1 SMP Debian 3.16.74-1 (2019-09-24) i686
>> GNU/Linux. Screen-shot below.
>
>Yeah, if you have the latest pull, then you have my fix for this
>problem.
>
>> Sorry to butt in.
>
>Butting in is what the bug tracker is for.  :-)
>
>-- 
>(domestic pets only, the antidote for overdose, milk.)
>   bloggy blog: http://lars.ingebrigtsen.no

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 1632 bytes --]

  reply	other threads:[~2019-10-31 18:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29  0:32 bug#37974: eww produces "error in process filter: Specified time is not representable" Stuart Little
2019-10-29  4:51 ` Stuart Little
2019-10-29 10:25   ` Stuart Little
2019-10-29 12:05     ` A.C.
2019-10-29 12:47       ` Lars Ingebrigtsen
2019-10-29 14:06         ` A.C.
2019-10-29 14:41           ` A.C.
2019-10-29 21:52           ` Lars Ingebrigtsen
2019-10-29 22:23             ` A.C.
2019-10-30 10:19               ` Colin Baxter
2019-10-30 11:01                 ` Lars Ingebrigtsen
2019-10-31 18:50                   ` A.C. [this message]
2019-11-01 13:46                     ` Lars Ingebrigtsen
2019-11-01  8:05 ` Paul Eggert
2019-11-01 23:22   ` Paul Eggert
2019-11-02  7:34     ` Eli Zaretskii

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=88F94981-2880-4ADE-A25D-800675800BA4@gmail.com \
    --to=achirvasub@gmail.com \
    --cc=37974@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=m43cap@yandex.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.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).