From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Juri Linkov <juri@linkov.net>
Cc: bpeeluk@yahoo.co.uk, larsi@gnus.org, 44236@debbugs.gnu.org
Subject: bug#44236: [PATCH] xdisp: Apply nobreak-char-display also to NARROW NO-BREAK SPACE U+202F
Date: Sun, 1 Nov 2020 14:43:32 -0800 (PST) [thread overview]
Message-ID: <6cf060bd-cd0c-46e2-807f-f537d20cf145@default> (raw)
In-Reply-To: <<83lffketlt.fsf@gnu.org>>
> Alternatively, if this new feature is so annoying, and people are
> unwilling to customize their Emacs to get the old behavior back, maybe
> we should make nobreak-char-display more than just a simple boolean,
> so that people could control which characters are and aren't
> emphasized?
(Not speaking to how annoying anything might be, here.)
`nobreak-char-display' is what it is. It can't be
expected to do more than it does, IMO. Its aim is
to highlight non-ASCII chars that look similar to
ASCII space and hyphen.
That's already too much, IMO. I've said before that
it's a weakness that users can't separate those two
(highlighting look-alikes for SPC and hyphen). They
shouldn't be hard-coupled together (IMO).
And I mentioned my library `highlight-chars.el',
which lets you highlight different sets of chars.
And code can control that. It sounds like that's
maybe what's being looked for here: highlight certain
chars in certain contexts (not just everywhere).
___
Description:
https://www.emacswiki.org/emacs/ShowWhiteSpace#HighlightChars
Code:
https://www.emacswiki.org/emacs/download/highlight-chars.el
next parent reply other threads:[~2020-11-01 22:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<20201026111348.773761-1-bpeeluk.ref@yahoo.co.uk>
[not found] ` <<20201026111348.773761-1-bpeeluk@yahoo.co.uk>
[not found] ` <<837drdeyss.fsf@gnu.org>
[not found] ` <<87h7q98p4q.fsf@mail.linkov.net>
[not found] ` <<87imapcjam.fsf@gnus.org>
[not found] ` <<87wnz4zz5k.fsf@mail.linkov.net>
[not found] ` <<83wnz4euxk.fsf@gnu.org>
[not found] ` <<87r1pcyib0.fsf@mail.linkov.net>
[not found] ` <<83lffketlt.fsf@gnu.org>
2020-11-01 22:43 ` Drew Adams [this message]
[not found] <20201026111348.773761-1-bpeeluk.ref@yahoo.co.uk>
2020-10-26 11:13 ` bug#44236: [PATCH] xdisp: Apply nobreak-char-display also to NARROW NO-BREAK SPACE U+202F Neil Roberts via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-26 16:29 ` Eli Zaretskii
2020-10-26 16:55 ` Drew Adams
2020-10-27 9:17 ` Neil Roberts via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-27 15:24 ` Eli Zaretskii
2020-11-01 8:20 ` Juri Linkov
2020-11-01 8:30 ` Juri Linkov
2020-11-01 13:12 ` Lars Ingebrigtsen
2020-11-01 15:16 ` Eli Zaretskii
2020-11-01 18:51 ` Juri Linkov
2020-11-01 19:29 ` Eli Zaretskii
2020-11-01 19:40 ` Juri Linkov
2020-11-01 19:52 ` Eli Zaretskii
2020-11-01 20:12 ` Juri Linkov
2020-11-03 18:44 ` Juri Linkov
2020-11-03 21:07 ` Basil L. Contovounesios
2020-11-04 19:54 ` Juri Linkov
2020-11-01 18:53 ` Juri Linkov
2020-11-01 19:30 ` Eli Zaretskii
2020-11-01 19:41 ` Juri Linkov
2020-11-01 19:59 ` Eli Zaretskii
2020-11-01 19:41 ` Neil Roberts via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-01 20:00 ` Juri Linkov
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=6cf060bd-cd0c-46e2-807f-f537d20cf145@default \
--to=drew.adams@oracle.com \
--cc=44236@debbugs.gnu.org \
--cc=bpeeluk@yahoo.co.uk \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--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).