From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Roland Winkler Newsgroups: gmane.emacs.bugs Subject: bug#57712: 29.0.50; bibtex.el: Should `bibtex-parse-entry' handle curly braces inside fields? Date: Sun, 11 Sep 2022 00:11:28 -0500 Message-ID: <871qsi5wcf.fsf@gnu.org> References: <87k06b26iu.fsf@localhost> <87r10jrgf4.fsf@gnus.org> <87zgf75i32.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10979"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 57712@debbugs.gnu.org, Ihor Radchenko To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Sep 11 07:12:19 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oXFGT-0002gw-SM for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 11 Sep 2022 07:12:17 +0200 Original-Received: from localhost ([::1]:46752 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oXFGS-0001ZS-PS for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 11 Sep 2022 01:12:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53124) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oXFGG-0001Z8-5M for bug-gnu-emacs@gnu.org; Sun, 11 Sep 2022 01:12:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:51915) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oXFGE-0003wo-M5 for bug-gnu-emacs@gnu.org; Sun, 11 Sep 2022 01:12:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oXFGE-0008GV-43 for bug-gnu-emacs@gnu.org; Sun, 11 Sep 2022 01:12:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Roland Winkler Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 11 Sep 2022 05:12:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57712 X-GNU-PR-Package: emacs Original-Received: via spool by 57712-submit@debbugs.gnu.org id=B57712.166287309831741 (code B ref 57712); Sun, 11 Sep 2022 05:12:02 +0000 Original-Received: (at 57712) by debbugs.gnu.org; 11 Sep 2022 05:11:38 +0000 Original-Received: from localhost ([127.0.0.1]:40614 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oXFFq-0008Fs-4s for submit@debbugs.gnu.org; Sun, 11 Sep 2022 01:11:38 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:43400) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oXFFn-0008EF-Dc for 57712@debbugs.gnu.org; Sun, 11 Sep 2022 01:11:37 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52402) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oXFFh-0003wD-TI; Sun, 11 Sep 2022 01:11:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:In-Reply-To:Date:References:Subject:To: From; bh=9N2H1eKECub5YJy+lNccfCTx2OTPQKHFIomQpaV/L+Y=; b=jG6UQHNWNqROSrwYJ0ds EIA7mPHCeoBy0NUBb93pYm5lxHMjH9BPoEB+BfJ2h4Pv3Z75ZDidZMhHQHYbNviQD/wkeT9CWRVft Cl4v75WZ2BdG4YBzypIoNN//v1HKGIMnoFQlUevqQHFpA0GZe6jIjCBRQZrZr2FierYyfknEhIF/z xlaAz+m1eJ2frDmammxH21U6gvIdxLlwk+ABXTePAypjqGCd0KxiY/kNDWsLvFSnv7nLegReCCjjr a5Zt1LR59Sxddnte6yKSItoOgzNwcBD+itGI6Q1mWonNDZqsYpi4CoQDKhxTcwV5NHVGFMkWZeblI 4Hilx4DhGxRNVQ==; Original-Received: from [2600:1700:5650:f790::42] (port=57556 helo=regnitz) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oXFFh-0005Nu-Ea; Sun, 11 Sep 2022 01:11:29 -0400 In-Reply-To: <87zgf75i32.fsf@gnu.org> (Roland Winkler's message of "Sat, 10 Sep 2022 11:07:13 -0500") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:242124 Archived-At: On Sat, Sep 10 2022, Roland Winkler wrote: > I must be missing something. I looked at the original org bug report that triggered the present report. I guess that now I understand what the OP is concerned about. I believe that bibtex-parse-entry is not the right place to try to fix this. The problem is to define what an optional arg CONTENT should do. I do not know what the "basic org cite export processor" mentioned by the OP is doing in detail. But it reminds me of bibtex-summary which is the default value of bibtex-summary-function. This function generates a "human-readable" summary of a BibTeX entry. It uses the autokey machinery of bibtex-mode that was originally developed for generating keys for new BibTeX entries. But this machinery can easily be "misused" for things like bibtex-summary. The point is that it offers rather many options to customize what such a summary should look like. Say, an entry has 20 authors. Do you want to display three or four authors? Do you want to just put dots after the third author or "et al."? Should the author(s) come first or should the title come first? Should the year appear before or after the title? (Essentially, you can go through all the questions relevant for BibTeX style files; but the autokey machinery comes with the power of emacs :-) So I suggest that the "basic org cite export processor" could use something similar to bibtex-summary. But this should just be the default value of something similar to bibtex-summary-function so that users can customize this more easily. (Letting users define their personal bibtex-summary function is probably easier than trying to define some user variables that can control this. There are just too many possibilities how one might want to customize things. My personal bibtex-summary function does a couple things that nobody else might like, but they are important for me.)