From: "Roland Winkler" <winkler@gnu.org>
To: Brian Elmegaard <be@mek.dtu.dk>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"47455@debbugs.gnu.org" <47455@debbugs.gnu.org>
Subject: bug#47455: 27.1; bibtex mode - citation key generation - non-ascii characters
Date: Sun, 30 May 2021 16:39:16 -0500 [thread overview]
Message-ID: <1540.59554.339986.24756@gargle.gargle.HOWL> (raw)
In-Reply-To: <730b1644528547f78ea6910f882591d6@mek.dtu.dk>
On Fri May 28 2021 Brian Elmegaard wrote:
> I understand your reasoning about this being an issue with the
> tools used. In auctex I can also enter \newcommand{\ü}{u} without
> being warned that it will not work with latex.
>
> The warning seems to be a good idea to me as well.
I realized:
One can also instruct font-lock to use for non-ascii characters
something like font-lock-warning-face (based on a user option for
enabling this behavior).
And Auctex could do the same.
However this fails with something like the unicode character
'ZERO WIDTH SPACE' (which has fooled me occassionally in the very
context we are discussing here). Is it possible to instruct emacs
to make such "hidden characters" more easily visible, say by using
some display property?
The fontification could also be encapsulated in a minor mode that
one could use for \(Bib\|La\)?TeX files.
Maybe such a minor mode exists already and I am right now
reinventing the wheel?
next prev parent reply other threads:[~2021-05-30 21:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 21:26 bug#47455: 27.1; bibtex mode - citation key generation - non-ascii characters Brian Elmegaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-18 16:05 ` Lars Ingebrigtsen
2021-05-18 19:00 ` Roland Winkler
2021-05-24 22:04 ` Lars Ingebrigtsen
2021-05-26 18:56 ` Roland Winkler
2021-05-28 7:17 ` Brian Elmegaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-30 21:39 ` Roland Winkler [this message]
2021-05-31 5:48 ` Lars Ingebrigtsen
2021-06-01 9:14 ` Arash Esbati
2021-06-01 14:37 ` Roland Winkler
2022-12-30 6:34 ` Roland Winkler
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=1540.59554.339986.24756@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=47455@debbugs.gnu.org \
--cc=be@mek.dtu.dk \
--cc=larsi@gnus.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).