GNU bug report logs - #30722
parse-time-string fails on Windows for some values.

Previous Next

Package: emacs;

Reported by: Jacob MacDonald <jaccarmac <at> gmail.com>

Date: Tue, 6 Mar 2018 00:47:02 UTC

Severity: normal

Tags: notabug

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

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

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

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#30722; Package emacs. (Tue, 06 Mar 2018 00:47:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Jacob MacDonald <jaccarmac <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Tue, 06 Mar 2018 00:47:02 GMT) Full text and rfc822 format available.

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

From: Jacob MacDonald <jaccarmac <at> gmail.com>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: parse-time-string fails on Windows for some values.
Date: Tue, 06 Mar 2018 00:46:22 +0000

[Message part 1 (text/plain, inline)]
Reporting from my home machine so system information here isn't useful
unfortunately, sorry. I can paste information from the Windows box I
experienced this on tomorrow.

To reproduce: On a Windows version of Emacs:

Evaluate (parse-time-string "2018-03-05")

A list of all nils is returned.

Removing the lexical-binding from parse-time.el solves the problem.
lexical-binding seems to have no effect on Linux.

[Message part 2 (text/html, inline)]
Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#30722; Package emacs. (Tue, 06 Mar 2018 03:40:02 GMT) Full text and rfc822 format available.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jacob MacDonald <jaccarmac <at> gmail.com>
Cc: 30722 <at> debbugs.gnu.org
Subject: Re: bug#30722: parse-time-string fails on Windows for some values.
Date: Tue, 06 Mar 2018 05:39:03 +0200

> From: Jacob MacDonald <jaccarmac <at> gmail.com>
> Date: Tue, 06 Mar 2018 00:46:22 +0000
> 
> To reproduce: On a Windows version of Emacs:
> 
> Evaluate (parse-time-string "2018-03-05")
> 
> A list of all nils is returned.

In what version of Emacs do you see this?  I cannot reproduce neither
in the current emacs-26 branch nor on master.
Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#30722; Package emacs. (Tue, 06 Mar 2018 05:57:02 GMT) Full text and rfc822 format available.

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

From: Jacob MacDonald <jaccarmac <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 30722 <at> debbugs.gnu.org
Subject: Re: bug#30722: parse-time-string fails on Windows for some values.
Date: Tue, 06 Mar 2018 05:55:44 +0000

[Message part 1 (text/plain, inline)]
26.0.91. Haven't built it totally clean yet, will try that way if no one
else can dupe. Maybe there's a stale variable in my build process
somewhere, but I thought being able to toggle the but with scope types was
a signal against that possibility.

On Mon, Mar 5, 2018, 21:39 Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Jacob MacDonald <jaccarmac <at> gmail.com>
> > Date: Tue, 06 Mar 2018 00:46:22 +0000
> >
> > To reproduce: On a Windows version of Emacs:
> >
> > Evaluate (parse-time-string "2018-03-05")
> >
> > A list of all nils is returned.
>
> In what version of Emacs do you see this?  I cannot reproduce neither
> in the current emacs-26 branch nor on master.
>

[Message part 2 (text/html, inline)]
Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#30722; Package emacs. (Tue, 06 Mar 2018 15:35:02 GMT) Full text and rfc822 format available.

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

From: Noam Postavsky <npostavs <at> gmail.com>
To: Jacob MacDonald <jaccarmac <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 30722 <at> debbugs.gnu.org
Subject: Re: bug#30722: parse-time-string fails on Windows for some values.
Date: Tue, 6 Mar 2018 10:34:26 -0500

On Tue, Mar 6, 2018 at 12:55 AM, Jacob MacDonald <jaccarmac <at> gmail.com> wrote:
> 26.0.91. Haven't built it totally clean yet, will try that way if no one
> else can dupe. Maybe there's a stale variable in my build process somewhere,
> but I thought being able to toggle the but with scope types was a signal
> against that possibility.

I can't reproduce on my Windows build of the emacs-26 branch either.
Just taking a quick look at the code, I don't see anything
w32-specific.
Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#30722; Package emacs. (Tue, 06 Mar 2018 15:51:02 GMT) Full text and rfc822 format available.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jacob MacDonald <jaccarmac <at> gmail.com>
Cc: 30722 <at> debbugs.gnu.org
Subject: Re: bug#30722: parse-time-string fails on Windows for some values.
Date: Tue, 06 Mar 2018 17:50:09 +0200

> From: Jacob MacDonald <jaccarmac <at> gmail.com>
> Date: Tue, 06 Mar 2018 05:55:44 +0000
> Cc: 30722 <at> debbugs.gnu.org
> 
> 26.0.91. Haven't built it totally clean yet, will try that way if no one else can dupe. Maybe there's a stale variable
> in my build process somewhere, but I thought being able to toggle the but with scope types was a signal
> against that possibility.

Does this happen with any date formatted as YYYY-MM-DD, or just with
some?  If the latter, can you try figuring out which ones fail?
Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#30722; Package emacs. (Tue, 06 Mar 2018 15:52:02 GMT) Full text and rfc822 format available.

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

From: Jacob MacDonald <jaccarmac <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 30722 <at> debbugs.gnu.org
Subject: Re: bug#30722: parse-time-string fails on Windows for some values.
Date: Tue, 06 Mar 2018 15:50:56 +0000

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

On Tue, Mar 6, 2018, 09:50 Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Jacob MacDonald <jaccarmac <at> gmail.com>
> > Date: Tue, 06 Mar 2018 05:55:44 +0000
> > Cc: 30722 <at> debbugs.gnu.org
> >
> > 26.0.91. Haven't built it totally clean yet, will try that way if no one
> else can dupe. Maybe there's a stale variable
> > in my build process somewhere, but I thought being able to toggle the
> but with scope types was a signal
> > against that possibility.
>
> Does this happen with any date formatted as YYYY-MM-DD, or just with
> some?  If the latter, can you try figuring out which ones fail?
>

[Message part 2 (text/html, inline)]
Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#30722; Package emacs. (Tue, 06 Mar 2018 17:00:02 GMT) Full text and rfc822 format available.

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

From: Jacob MacDonald <jaccarmac <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 30722 <at> debbugs.gnu.org
Subject: Re: bug#30722: parse-time-string fails on Windows for some values.
Date: Tue, 06 Mar 2018 16:58:45 +0000

[Message part 1 (text/plain, inline)]
I can confirm that a fresh build solves my problem. Diffed the elisp files
against each other to make sure, the problem must be in my compile process
somewhere.

On Tue, Mar 6, 2018, 09:50 Jacob MacDonald <jaccarmac <at> gmail.com> wrote:

> Every one.
>
> On Tue, Mar 6, 2018, 09:50 Eli Zaretskii <eliz <at> gnu.org> wrote:
>
>> > From: Jacob MacDonald <jaccarmac <at> gmail.com>
>> > Date: Tue, 06 Mar 2018 05:55:44 +0000
>> > Cc: 30722 <at> debbugs.gnu.org
>> >
>> > 26.0.91. Haven't built it totally clean yet, will try that way if no
>> one else can dupe. Maybe there's a stale variable
>> > in my build process somewhere, but I thought being able to toggle the
>> but with scope types was a signal
>> > against that possibility.
>>
>> Does this happen with any date formatted as YYYY-MM-DD, or just with
>> some?  If the latter, can you try figuring out which ones fail?
>>
>

[Message part 2 (text/html, inline)]
Added tag(s) notabug; removed tag(s) moreinfo. Request was from Glenn Morris <rgm <at> gnu.org> to control <at> debbugs.gnu.org. (Tue, 06 Mar 2018 17:37:02 GMT) Full text and rfc822 format available.
bug closed, send any further explanations to 30722 <at> debbugs.gnu.org and Jacob MacDonald <jaccarmac <at> gmail.com> Request was from Glenn Morris <rgm <at> gnu.org> to control <at> debbugs.gnu.org. (Tue, 06 Mar 2018 17:37:02 GMT) Full text and rfc822 format available.
Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#30722; Package emacs. (Tue, 06 Mar 2018 17:51:01 GMT) Full text and rfc822 format available.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jacob MacDonald <jaccarmac <at> gmail.com>
Cc: 30722-done <at> debbugs.gnu.org
Subject: Re: bug#30722: parse-time-string fails on Windows for some values.
Date: Tue, 06 Mar 2018 19:49:43 +0200

> From: Jacob MacDonald <jaccarmac <at> gmail.com>
> Date: Tue, 06 Mar 2018 16:58:45 +0000
> Cc: 30722 <at> debbugs.gnu.org
> 
> I can confirm that a fresh build solves my problem. Diffed the elisp files against each other to make sure, the
> problem must be in my compile process somewhere.

OK, thanks.  I'm therefore closing this bug report.
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Wed, 04 Apr 2018 11:24:04 GMT) Full text and rfc822 format available.
This bug report was last modified 7 years and 81 days ago.

Previous Next

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