From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Sebastien Vauban <sva-news@mygooglest.com>
Cc: "16177@debbugs.gnu.org" <16177@debbugs.gnu.org>
Subject: bug#16177: [External] : bug#16177: 24.3.50; Display glyphs for hard spaces in color
Date: Sun, 30 May 2021 15:00:32 +0000 [thread overview]
Message-ID: <SA2PR10MB4474A4701EE18DD442B4F402F3209@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <874kek4w6w.fsf@gnus.org>
> > To get hard spaces (aka nbsp) highlighted, you need to add `spaces' to
> > `whitespace-style': [...] Narrow nbsp aren't highlighted.
>
> I guess this is a feature request to have whitespace-mode being able to
> emphasise the space characters that aren't the normal ASCII space
> separately. That (surprisingly enough) doesn't seem to be an option?
> And, indeed, whitespace-mode only knows about SPACE and NO-BREAK SPACE,
> and none of the other space characters.
>
> So I think a new whitespace-style should be added -- like `other-space',
> for all the spaces that aren't SPACE.
>
> However, the original impetus for doing this may be somewhat lessened by
> Emacs now defaulting to highlighting other spaces in a different way by
> default -- even without whitespace-mode.
The problem/question has been raised several times.
From bug #9790 (10 years ago):
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=9790#21
Various posts in this thread essentially propose different
blanket approaches, i.e., paint something with a broad brush.
Some want such brushwork in some contexts; others don't.
What's needed, I think, are (1) a fine-grained mechanism to
control which chars get highlighted and how and where/when,
(2) default applications of that mechanism to specific contexts,
and (3) user ability to control things.
No broad brushwork will be satisfactory, I think. I think
some form of #1 is the starting point - without that, I
don't see a good solution.
I mentioned my library `highlight-chars.el', which provides
support for #1: ways to highlight any set of chars, and
control where/when/whether that's done. Maybe take a look
at what it offers, as food for thought or even perhaps reuse?
That bug, reported by Chong Yidong, follows from an
emacs-devel discussion of the problem/question. And
that bug and similar/~duplicate ones are still open.
The overall approach/strategy should be discussed again,
perhaps, and a plan decided on wrt fixing the problem.
See also:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=14481#8
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=16177#8
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44236#11
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44236#75
prev parent reply other threads:[~2021-05-30 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 14:01 bug#16177: 24.3.50; Display glyphs for hard spaces in color Sebastien Vauban
2013-12-17 15:31 ` Drew Adams
2021-05-30 5:39 ` Lars Ingebrigtsen
2021-05-30 15:00 ` Drew Adams [this message]
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=SA2PR10MB4474A4701EE18DD442B4F402F3209@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=16177@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=sva-news@mygooglest.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).