all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jacob MacDonald <jaccarmac@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30722@debbugs.gnu.org
Subject: bug#30722: parse-time-string fails on Windows for some values.
Date: Tue, 06 Mar 2018 16:58:45 +0000	[thread overview]
Message-ID: <CACy6W0Dfr7xNt7aGinxj+4LTNubRCrdCi_fKWYp1i2MawdSEfQ@mail.gmail.com> (raw)
In-Reply-To: <CACy6W0D_WZ7qQHB8TK9WUabmFFuTO72yH-fZC3CAj212EePqkQ@mail.gmail.com>

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

  reply	other threads:[~2018-03-06 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06  0:46 bug#30722: parse-time-string fails on Windows for some values Jacob MacDonald
2018-03-06  3:39 ` Eli Zaretskii
2018-03-06  5:55   ` Jacob MacDonald
2018-03-06 15:34     ` Noam Postavsky
2018-03-06 15:50     ` Eli Zaretskii
2018-03-06 15:50       ` Jacob MacDonald
2018-03-06 16:58         ` Jacob MacDonald [this message]
2018-03-06 17:49           ` 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

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

  git send-email \
    --in-reply-to=CACy6W0Dfr7xNt7aGinxj+4LTNubRCrdCi_fKWYp1i2MawdSEfQ@mail.gmail.com \
    --to=jaccarmac@gmail.com \
    --cc=30722@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.