unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: gojjoe2@googlemail.com
Cc: 39686@debbugs.gnu.org
Subject: bug#39686: 25.2; Wrong behaviour of bibtex-autokey-name-change-strings
Date: Fri, 21 Feb 2020 08:06:01 -0600	[thread overview]
Message-ID: <58313.86150.684238.24143@gargle.gargle.HOWL> (raw)
In-Reply-To: <86569ef7-ff5f-4a3a-bbbd-3e1a3990bce9@gmail.com>

On Fri Feb 21 2020 gojjoe2@googlemail.com wrote:
> Yes it does, at least for the specific problem I found with
> "\oe". Thank you very much!

Thanks for for confirming it fixes your problem.

> Can you tell me where to insert this redefinition in my init file,
> while I wait for the next Emacs version? I tried adding it to my
> own bibtex-hook and to "eval-after-load 'bibtex ...", but it
> doesn't seem to have any effect in either. At the moment is called
> directly in the init file.

Bibtex-mode uses the variable bibtex-autokey-transcriptions to
define the default values of `bibtex-autokey-name-change-strings'
and `bibtex-autokey-titleword-change-strings'.  So something like
eval-after-load will work only if it deals with all three variables.
Say, you first set bibtex-autokey-transcriptions to its new value;
then you use this to set `bibtex-autokey-name-change-strings' and
`bibtex-autokey-titleword-change-strings'.

It is probably easier to simply set bibtex-autokey-transcriptions in
your init file to its new value.  Normally, emacs should load
bibtex-mode later.  Then it will use your value of
bibtex-autokey-transcriptions to set the values of
`bibtex-autokey-name-change-strings' and
`bibtex-autokey-titleword-change-strings'.





  reply	other threads:[~2020-02-21 14:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20  4:54 bug#39686: 25.2; Wrong behaviour of bibtex-autokey-name-change-strings Roland Winkler
     [not found] ` <handler.39686.B.158217451717286.ack@debbugs.gnu.org>
2020-02-20  5:04   ` Roland Winkler
2020-02-21  9:22     ` gojjoe2--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-02-21 14:06       ` Roland Winkler [this message]
2020-02-21 14:08         ` gojjoe2--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-02-21 14:13     ` Roland Winkler
2020-02-21 15:01       ` Eli Zaretskii
2020-02-21 19:50         ` Roland Winkler
2020-02-22  9:12           ` Eli Zaretskii
2020-03-06  8:46             ` Roland Winkler
2020-02-21 16:05 ` Mattias Engdegård
2020-02-21 20:03   ` Roland Winkler
2020-02-21 20:43     ` Mattias Engdegård
2020-02-21 21:03       ` Roland Winkler
2020-02-21 21:32         ` Mattias Engdegård

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=58313.86150.684238.24143@gargle.gargle.HOWL \
    --to=winkler@gnu.org \
    --cc=39686@debbugs.gnu.org \
    --cc=gojjoe2@googlemail.com \
    /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).