all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Francesco Potortì" <pot@gnu.org>
Cc: 44614@debbugs.gnu.org
Subject: bug#44614: 26.3; bibtex convert case undefined
Date: Sat, 14 Nov 2020 17:33:26 +0100	[thread overview]
Message-ID: <87v9e7yk2x.fsf@gnus.org> (raw)
In-Reply-To: <E1kdWt7-00EE0o-Tc@tucano.isti.cnr.it> ("Francesco Potortì"'s message of "Fri, 13 Nov 2020 12:05:05 +0100")

Francesco Potortì <pot@gnu.org> writes:

> An old version of bibtex.el (last copyright 1997) uniquified cases based
> on the bibtex-unify-case-convert variable, which is now removed.
>
> This is unfortunate, and in my opinion a bug.

I tried to poke around to see whether there's any reason the variable
was removed, but I can't find any mention of it in the Emacs tree, so
it's possible that the in-tree version of bibtex.el never had the
variable?

> Looking at the old code, I see that the current behaviour is the same as
> the old 'identity value for the mentioned variable.  I am working on a
> local patch for reverting to the old behaviour.  After I finish, I can
> provide it, if there is any hope of it to be accepted.
>
> Here is the old definition:
>
> (defcustom bibtex-unify-case-convert 'downcase
>   "*Function called when unifying case on entry and field names.
> This variable is buffer-local."

Sure; I think (re-)introducing such a variable would make sense.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-11-14 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 11:05 bug#44614: 26.3; bibtex convert case undefined Francesco Potortì
2020-11-14 16:33 ` Lars Ingebrigtsen [this message]
2020-11-14 18:47   ` Francesco Potortì
2020-11-16 21:36     ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9e7yk2x.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=44614@debbugs.gnu.org \
    --cc=pot@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.