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

Previous Next

Full log

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)]

Previous Next

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