From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ryan Kavanagh <rak@debian.org>
Cc: 36252@debbugs.gnu.org
Subject: bug#36252: 26.1; bibtex-generate-autokey does not use use date field
Date: Mon, 16 Sep 2019 23:01:02 +0200 [thread overview]
Message-ID: <87k1a8q7ld.fsf@gnus.org> (raw)
In-Reply-To: <m3v9w33gll.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 15 Jul 2019 09:24:38 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Ryan Kavanagh <rak@debian.org> writes:
>
>> On Sat, Jul 06, 2019 at 04:55:47PM +0200, Lars Ingebrigtsen wrote:
>>> (This reminds me -- Emacs should really have a parser that can parse
>>> all ISO8601 variants. There's parse-iso8601-time-string, but it only
>>> handles the simplest of the formats...)
>>
>> Perhaps that should be the first step, and then the committed fix to
>> this bug can just use that.
>
> I've implemented a proper iso8601 parser now, but hasn't merged with the
> Emacs trunk yet because I haven't done the entire test suite yet. It's
> on the scratch/iso8601 branch if you want to check it out.
The iso8601 parser is in the trunk now, so if you could rework your
patch based on that, that'd be nice. The function to use is
`iso8601-parse'.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-16 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 20:23 bug#36252: 26.1; bibtex-generate-autokey does not use use date field Ryan Kavanagh
2019-07-06 14:52 ` Lars Ingebrigtsen
2019-07-06 14:55 ` Lars Ingebrigtsen
2019-07-15 0:34 ` Ryan Kavanagh
2019-07-15 7:24 ` Lars Ingebrigtsen
2019-09-16 21:01 ` Lars Ingebrigtsen [this message]
2020-08-10 11:01 ` Lars Ingebrigtsen
2020-09-14 15:02 ` Lars Ingebrigtsen
2020-12-05 9:20 ` Patrick M. Niedzielski
2020-12-06 9:25 ` Colin Baxter
2020-12-07 6:18 ` Roland Winkler
2020-12-06 13:19 ` Lars Ingebrigtsen
2020-12-07 6:20 ` Roland Winkler
2020-12-07 15:14 ` Lars Ingebrigtsen
2020-12-11 15:04 ` Roland Winkler
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=87k1a8q7ld.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36252@debbugs.gnu.org \
--cc=rak@debian.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).