unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: "Daniel \=\?utf-8\?Q\?Mart\=C3\=ADn"?= <mardani29@yahoo.es>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: minor mode for highlighting character classes such as non-ascii (bug 47455)
Date: Tue, 1 Jun 2021 12:34:56 -0500	[thread overview]
Message-ID: <28608.63306.862705.24758@gargle.gargle.HOWL> (raw)
In-Reply-To: <m1bl8pbk6h.fsf@yahoo.es>

On Tue Jun 1 2021 Daniel Martín wrote:
> There's already a feature in the display engine that shows certain
> non-ASCII characters with a special face.  For example, U+00A0 (no-break
> space) is shown with the ‘nobreak-space’ face, U+00AD (soft hyphen),
> ‘U+2010’ (hyphen), and ‘U+2011’ (non-breaking hyphen) are shown with the
> ‘nobreak-hyphen’ face.  Perhaps your suggestion could be a
> backwards-compatible extension to this hardcoded display mechanism.
> 
> Another option is to simply instruct users to use Hi Lock mode with
> "[^[:ascii:]]".

Thanks, Hi Lock mode seems to be already a close match.  I'll look
at this more closely.

The bug report is related to the fact that \(Bib\|La\)?TeX chokes on
any non-ascii characters.  Nonetheless, non-ascii characters can end
up in such files for all kinds of reasons.  So the idea is to have
something like a minor mode that highlights any non-ascii characters
so that this effectively warns the user about the presence of such
characters.

Personally, I have been fooled in particular by unicode 'ZERO WIDTH
SPACE' which probably requires special treatment.  Could it also
make sense to give this particular character a (possibly configurable)
treatment by the display engine?  (I know nothing about the display
engine.)



  reply	other threads:[~2021-06-01 17:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 16:16 minor mode for highlighting character classes such as non-ascii (bug 47455) Roland Winkler
2021-06-01 16:31 ` Eli Zaretskii
2021-06-01 16:32 ` Óscar Fuentes
2021-06-01 16:48   ` Eli Zaretskii
2021-06-01 16:49   ` [External] : " Drew Adams
2021-06-01 16:53     ` Eli Zaretskii
2021-06-01 18:07       ` Drew Adams
2021-06-01 18:20         ` Eli Zaretskii
2021-06-01 16:53 ` Daniel Martín
2021-06-01 17:34   ` Roland Winkler [this message]
2021-06-01 17:39     ` Eli Zaretskii
2021-06-01 17:56       ` Roland Winkler
2021-06-01 20:51 ` Juri Linkov
2021-06-01 21:45   ` 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=28608.63306.862705.24758@gargle.gargle.HOWL \
    --to=winkler@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mardani29@yahoo.es \
    /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).