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: Mon, 12 Sep 2022 08:50:21 -0500 Message-ID: <8735cw3dnm.fsf@gnu.org> References: <87k06b26iu.fsf@localhost> <87r10jrgf4.fsf@gnus.org> <87zgf75i32.fsf@gnu.org> <871qsi5wcf.fsf@gnu.org> <87bkrlw4ml.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22978"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 57712@debbugs.gnu.org, Lars Ingebrigtsen To: Ihor Radchenko Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Sep 12 15:51:25 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 1oXjqP-0005ou-2T for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 12 Sep 2022 15:51:25 +0200 Original-Received: from localhost ([::1]:34138 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oXjqO-0004sC-45 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 12 Sep 2022 09:51:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55934) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oXjq3-0004Zj-Kv for bug-gnu-emacs@gnu.org; Mon, 12 Sep 2022 09:51:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55982) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oXjq2-0003YL-4u for bug-gnu-emacs@gnu.org; Mon, 12 Sep 2022 09:51:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oXjq1-0007Pa-V6 for bug-gnu-emacs@gnu.org; Mon, 12 Sep 2022 09:51:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Roland Winkler Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 12 Sep 2022 13:51:01 +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.166299063228453 (code B ref 57712); Mon, 12 Sep 2022 13:51:01 +0000 Original-Received: (at 57712) by debbugs.gnu.org; 12 Sep 2022 13:50:32 +0000 Original-Received: from localhost ([127.0.0.1]:44681 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oXjpY-0007Oq-63 for submit@debbugs.gnu.org; Mon, 12 Sep 2022 09:50:32 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:42554) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oXjpW-0007OX-2F for 57712@debbugs.gnu.org; Mon, 12 Sep 2022 09:50:30 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35664) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oXjpP-0003Rx-Vj; Mon, 12 Sep 2022 09:50:24 -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=mBr1WQgl4AAkWHaCDLVUFpE0A49GumwmrU7R3ctxJCs=; b=LK5nMRa49TLhofaJzRGw kMeyS+vJcPdBCiuM1Go3c0PxVhJ7dSUfip7NDm/fJivwpjdM8IL1HrIcPlghSdewP250zMSjuqsYS 512cSVet/rytZ1QwLyGDmhdxizdZExl855h25K2sDp0pItagORAbY0Yw1VUrKoC73FuxzlxP2YCVb h1CyqxcdWzTdS+ztbd1S4fKpbVApba0us/ZmpCLrW9MI3am0GQSUd2U/hSNf+/I1NtkdBLXYy+fN7 epXt6X1mFKNELKHw1W6HFl0KuJBDfLawB1P9gmtlb6N3O2MgRQ1GqPHwXDUIsPYPvTvNx6YJY11Or PFYZAagNKtJV7Q==; Original-Received: from [2600:1700:5650:f790::42] (port=60096 helo=regnitz) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oXjpP-00057o-Cc; Mon, 12 Sep 2022 09:50:23 -0400 In-Reply-To: <87bkrlw4ml.fsf@localhost> (Ihor Radchenko's message of "Mon, 12 Sep 2022 13:20:18 +0800") 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:242276 Archived-At: On Mon, Sep 12 2022, Ihor Radchenko wrote: > To clarify, I do not expect bibtex-parse-entry to strip the braces. What > I'd like to see is _parsing_ braces (say, as sexp) and other special > BibTeX syntax. At least, as long as appropriate option is passed to > bibtex-parse-entry. Can you give some examples of what you believe bibtex-parse-entry should do if it had an optional arg CONTENT? What should it return instead of what it returns without such an arg? > bibtex-summary approach might be an option, although it is clearly an > abuse and begs for future bugs. My point is: the meaning of CONTENT may largely depend on what the caller of bibtex-parse-entry wants to achieve. What appears perfectly reasonable from your perspective may be meaningless from another perspective. That's why the autokey machinery comes with lots of options in terms of user variables, plus the option of letting the user ignore all of this and define her own function (both for automatically generating a key and for generating a summary for an entry). -- It's not a perfect solution. But it has worked well for many years. A single arg CONTENT (trying to guess "do what I mean") cannot cover all this in a satisfactory way.