From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: Neil Roberts <bpeeluk@yahoo.co.uk>, 44236@debbugs.gnu.org
Subject: bug#44236: [PATCH] xdisp: Apply nobreak-char-display also to NARROW NO-BREAK SPACE U+202F
Date: Sun, 01 Nov 2020 14:12:49 +0100 [thread overview]
Message-ID: <87imapcjam.fsf@gnus.org> (raw)
In-Reply-To: <87h7q98p4q.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 01 Nov 2020 10:20:20 +0200")
Juri Linkov <juri@linkov.net> writes:
> The intention of nobreak-space is to warn the user about confusable
> characters in writable buffers. But why highlight such characters
> in read-only Dired buffers?
Perhaps `special-mode' should switch this highlighting off?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-11-01 13:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[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-10-28 11:37 ` bug#44236: [PATCH] xdisp: Apply nobreak-char-display to all characters of blankp Neil Roberts via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-30 12:14 ` bug#44236: (no subject) Lars Ingebrigtsen
2020-11-01 8:20 ` bug#44236: [PATCH] xdisp: Apply nobreak-char-display also to NARROW NO-BREAK SPACE U+202F Juri Linkov
2020-11-01 8:30 ` Juri Linkov
2020-11-01 13:12 ` Lars Ingebrigtsen [this message]
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
[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
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=87imapcjam.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44236@debbugs.gnu.org \
--cc=bpeeluk@yahoo.co.uk \
--cc=juri@linkov.net \
/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).