bug#30722: parse-time-string fails on Windows for some values.

bug#30722: parse-time-string fails on Windows for some values.

[Jacob MacDonald]

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

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.

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

bug#30722: parse-time-string fails on Windows for some values.

[Eli Zaretskii]

> From: Jacob MacDonald <jaccarmac@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.

bug#30722: parse-time-string fails on Windows for some values.

[Jacob MacDonald]

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

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@gnu.org> wrote:

> > From: Jacob MacDonald <jaccarmac@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.
>

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

bug#30722: parse-time-string fails on Windows for some values.

[Noam Postavsky]

On Tue, Mar 6, 2018 at 12:55 AM, Jacob MacDonald <jaccarmac@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.

bug#30722: parse-time-string fails on Windows for some values.

[Eli Zaretskii]

> From: Jacob MacDonald <jaccarmac@gmail.com>
> Date: Tue, 06 Mar 2018 05:55:44 +0000
> Cc: 30722@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?

bug#30722: parse-time-string fails on Windows for some values.

[Jacob MacDonald]

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

Every one.

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

> > From: Jacob MacDonald <jaccarmac@gmail.com>
> > Date: Tue, 06 Mar 2018 05:55:44 +0000
> > Cc: 30722@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?
>

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

bug#30722: parse-time-string fails on Windows for some values.

[Jacob MacDonald]

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

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@gmail.com> wrote:

> Every one.
>
> On Tue, Mar 6, 2018, 09:50 Eli Zaretskii <eliz@gnu.org> wrote:
>
>> > From: Jacob MacDonald <jaccarmac@gmail.com>
>> > Date: Tue, 06 Mar 2018 05:55:44 +0000
>> > Cc: 30722@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?
>>
>

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

bug#30722: parse-time-string fails on Windows for some values.

[Eli Zaretskii]

> From: Jacob MacDonald <jaccarmac@gmail.com>
> Date: Tue, 06 Mar 2018 16:58:45 +0000
> Cc: 30722@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.