From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: "Patrick M. Niedzielski" <patrick@pniedzielski.net>,
Ryan Kavanagh <rak@debian.org>,
36252@debbugs.gnu.org
Subject: bug#36252: 26.1; bibtex-generate-autokey does not use use date field
Date: Mon, 07 Dec 2020 16:14:43 +0100 [thread overview]
Message-ID: <87tusxhcm4.fsf@gnus.org> (raw)
In-Reply-To: <51654.98578.572978.24525@gargle.gargle.HOWL> (Roland Winkler's message of "Mon, 7 Dec 2020 00:20:54 -0600")
"Roland Winkler" <winkler@gnu.org> writes:
> On Sun Dec 6 2020 Lars Ingebrigtsen wrote:
>> Looks reasonable to me. I've added Roland to the Cc's; perhaps he
>> has some comments.
>
> [Thank you Lars, I haven't subscribed to the bug-gnu-emacs mailing
> list. Lately bug reports for bibtex.el seem to be popular. Can you
> please drop me a note if you see more bug reports for bibtex.el?
> Thanks!]
Sure; I'm just slowly working my way through old bug reports, which is
why you're seeing more of these now. :-) I'll keep Cc-ing you on the
bibtex stuff.
> A few days ago I installed in master a related patch that I had
> lying around for some time. I believe it addresses the question of
> searching the date and year field in a cleaner way by passing a list
> of field names to bibtex-text-in-field. But I didn't know the new
> iso8601 library. So that's the main purpose of the new patch
> attached below. (This patch is against the current version of
> bibtex.el in master.)
Looks good to me.
> Regarding the docstring of bibtex-generate-autokey: I am not sure
> this is the right place to elaborate on iso8601. bibtex.el assumes
> throughout that users are familiar with valid values for different
> fields.
Yup.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-07 15:14 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
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 [this message]
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=87tusxhcm4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36252@debbugs.gnu.org \
--cc=patrick@pniedzielski.net \
--cc=rak@debian.org \
--cc=winkler@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 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).