all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <f92capac@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Tino Calancha <f92capac@gmail.com>,
	Andreas Schwab <schwab@suse.de>,
	21229@debbugs.gnu.org,
	Nicolas Richard <youngfrog@members.fsf.org>
Subject: bug#21229: 24.5; parse-time-string ignore PM/AM
Date: Wed, 12 Aug 2015 14:45:36 +0900 (JST)	[thread overview]
Message-ID: <alpine.LRH.2.20.1508121432210.20899@calancha-ilc.kek.jp> (raw)
In-Reply-To: <jwvbnedhl0s.fsf-monnier+emacsbugs@gnu.org>


At some point one decision (order to support) should be taken 
because MM DD need to be identified:
07-11, november 7th?
Maybe July 11th?

My propose is support
date +%F (%Y-%m-%d already in vanilla emacs)
and
date +%D (%m/%d/%y)

It is straightforward to extend my previous patch adding one rule to 
support:
%m/%d/%Y (%Y instead of %y)

I think that cover enough date formats.

I understand is hard to remember if %m/%d/%y or %d/%m/%y
is supported: the documentation string of parse-time-string should 
be updated to clearly point out what input strings are valid.

Tino

On Tue, 11 Aug 2015, Stefan Monnier wrote:

>>> It should be possible to add support for:
>>> "%m/%d/%y"
>> What about "%d/%m/%y"?
>
> Indeed.  I already bumped into such problems with parse-time-string
> where it seemed to return a completely bogus result until I realized
> that it picked a different ordering from the one I had.
>
> The problem exists for "a-b-c" as well, tho I can't remember ever seeing
> "YYYY-DD-MM" nor "MM-DD-YYYY" so if the year is spelled out as 4 digits,
> the "a-b-c" format is somewhat reliable (at least within my part of the
> world).
>
>
>        Stefan
>






  reply	other threads:[~2015-08-12  5:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10  8:19 bug#21229: 24.5; parse-time-string ignore PM/AM Tino Calancha
2015-08-10 17:29 ` Eli Zaretskii
2015-08-10 17:35   ` Tino Calancha
2015-08-10 17:46     ` Eli Zaretskii
2015-08-11  2:36       ` Tino Calancha
2015-08-11  8:32         ` Nicolas Richard
2015-08-11 10:37           ` Tino Calancha
2015-08-11 10:40             ` Andreas Schwab
2015-08-11 10:52               ` Tino Calancha
2015-08-11 11:00                 ` Andreas Schwab
2015-08-11 11:47                   ` Tino Calancha
2015-08-11 16:05               ` Stefan Monnier
2015-08-12  5:45                 ` Tino Calancha [this message]
2015-08-12 12:39                   ` Eli Zaretskii
2015-08-12 12:46                     ` Tino Calancha
2015-08-12 12:41                   ` Nicolas Richard
2020-08-24 18:35     ` Lars Ingebrigtsen

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=alpine.LRH.2.20.1508121432210.20899@calancha-ilc.kek.jp \
    --to=f92capac@gmail.com \
    --cc=21229@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@suse.de \
    --cc=youngfrog@members.fsf.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.