GNU bug report logs - #39686
25.2; Wrong behaviour of bibtex-autokey-name-change-strings

Previous Next

Package: emacs;

Reported by: "Roland Winkler" <winkler <at> gnu.org>

Date: Thu, 20 Feb 2020 04:56:02 UTC

Severity: normal

Found in version 25.2

Done: "Roland Winkler" <winkler <at> gnu.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: "Roland Winkler" <winkler <at> gnu.org>
To: Mattias Engdegård <mattiase <at> acm.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, gojjoe2 <at> googlemail.com, 39686 <at> debbugs.gnu.org
Subject: bug#39686: 25.2; Wrong behaviour of bibtex-autokey-name-change-strings
Date: Fri, 21 Feb 2020 14:03:29 -0600

On Fri Feb 21 2020 Mattias Engdegård wrote:
> Correct me if I'm wrong, but it looks like the assumption is that
> all possible \-sequences have been enumerated in that list. More
> likely, some kind of anchoring after the match is needed, like
> word-end ("\\>"). Then the matching order doesn't matter.

I am not sure I understand.  The idea in bibtex-autokey-transcriptions
is that each match of OLD-REGEXP is replaced in full by NEW-STRING.
Subexpressions are ignored.

In LaTeX syntax, OLD-REGEXP can appear anywhere inside what LaTeX
considers a word (which even may include spaces).  So to make things
more fool-proofed, it would be necessary to parse more carefully the
LaTeX code.  I do not think this effort is needed here as these
regexps have worked well for at least two decades.  The patch fixes
a minor problem of these regexps pointed out by the OP.  But
otherwise it preserves their spirit.
This bug report was last modified 5 years and 74 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.