all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Neil Roberts <bpeeluk@yahoo.co.uk>
Cc: 44236@debbugs.gnu.org
Subject: bug#44236: [PATCH] xdisp: Apply nobreak-char-display also to NARROW NO-BREAK SPACE U+202F
Date: Mon, 26 Oct 2020 09:55:59 -0700 (PDT)	[thread overview]
Message-ID: <046fa315-abf3-44e0-840d-73bf870d3c8f@default> (raw)
In-Reply-To: <837drdeyss.fsf@gnu.org>

> But what is the purpose of showing this character like we do with
> NBSP?  We do that with NBSP because otherwise it will be easy to
> interpret NBSP as a SPC: they have the same width and appearance on
> display.  By contrast, U+202F NARROW NO-BREAK SPACE is much thinner,
> and cannot be mistaken to be SPC.
> 
> OTOH, if we make U+202F stand out, then why not others, for example
> U+2007? or U+2060? or U+2002? or U+2003? or U+2009 etc.
> 
> IOW, we need to decide on the rationale for displaying these
> specially, and then we can decide which ones should have this applied.

I agree, both (1) that the main purpose of the current highlighting is to make no-break (aka hard) space stand out from ordinary space, and (2) that any additional highlighting needs a rationale.
___

FWIW -

My library highlight-chars.el lets you highlight particular chars in different ways, au choix.  And in particular, you can highlight just hard spaces or just hard hyphens (they need not be treated the same way).

https://www.emacswiki.org/emacs/download/highlight-chars.el





  reply	other threads:[~2020-10-26 16:55 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=046fa315-abf3-44e0-840d-73bf870d3c8f@default \
    --to=drew.adams@oracle.com \
    --cc=44236@debbugs.gnu.org \
    --cc=bpeeluk@yahoo.co.uk \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.