From: Yuri Khan <yuri.v.khan@gmail.com>
To: tomas@tuxteam.de
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
HASM <hasm@example.invalid>
Subject: Re: icalendar--datetime-to-iso-date (icalendar.el)
Date: Fri, 4 Nov 2016 15:49:58 +0600 [thread overview]
Message-ID: <CAP_d_8WtzU8C2RF_eF4W2v120GcGnzeaUytbq+3AT2NiBdeHag@mail.gmail.com> (raw)
In-Reply-To: <20161104083006.GB30312@tuxteam.de>
On Fri, Nov 4, 2016 at 3:30 PM, <tomas@tuxteam.de> wrote:
>> Shouldn't format in:
>> icalendar--datetime-to-iso-date (icalendar.el)
>> be:
>> "%04d%s%02d%s%02d"
>> instead of:
>> "%d%s%d%s%d"?
>
> That seems to make sense. After all, an ISO date looks like
> "2016-08-09" and not "2016-8-9".
>
> Consider reporting a bug with M-x report-emacs-bug.
Consider also that the only valid date separators are the empty string
and the hyphen-minus character, while the function in question uses
the space by default.
prev parent reply other threads:[~2016-11-04 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 13:27 icalendar--datetime-to-iso-date (icalendar.el) HASM
2016-11-04 8:30 ` tomas
2016-11-04 9:49 ` Yuri Khan [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP_d_8WtzU8C2RF_eF4W2v120GcGnzeaUytbq+3AT2NiBdeHag@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=hasm@example.invalid \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).