From: "Roland Winkler" <winkler@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: gojjoe2@googlemail.com, 39686@debbugs.gnu.org
Subject: bug#39686: 25.2; Wrong behaviour of bibtex-autokey-name-change-strings
Date: Fri, 21 Feb 2020 15:03:11 -0600 [thread overview]
Message-ID: <17807.59258.546985.24144@gargle.gargle.HOWL> (raw)
In-Reply-To: <6F3F5510-4567-47A2-B0AA-88E2FED57167@acm.org>
On Fri Feb 21 2020 Mattias Engdegård wrote:
> In LaTeX you can't just write 'b\oeuf'; it will complain that
> '\oeuf' is undefined. You have to write 'b\oe uf' or
> 'b{\oe}uf'. Thus there is a word break at the end.
In bibtex-mode, all this is used in the context of what is supposed
to represent names and titles of books and articles. The current
scheme has been in place for at least two decades and nobody
complained about this. (Note that the current thread is about
something else.) So I assume that what you are concerned about is
so rare (at least in the context of the autokey machinery) that it
is not worth the effort.
But feel free to provide a patch along these lines. However, that
patch should certainly go into master because it modifies the
current scheme.
next prev parent reply other threads:[~2020-02-21 21:03 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
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 [this message]
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=17807.59258.546985.24144@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=39686@debbugs.gnu.org \
--cc=gojjoe2@googlemail.com \
--cc=mattiase@acm.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 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).