all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: 9790@debbugs.gnu.org, Chong Yidong <cyd@gnu.org>
Subject: bug#9790: Cleaning up nobreak-char-display
Date: Tue, 08 Dec 2020 15:17:53 +0100	[thread overview]
Message-ID: <87czzkjsa6.fsf@gnus.org> (raw)
In-Reply-To: <87blf4908s.fsf@mail.linkov.net> (Juri Linkov's message of "Tue,  08 Dec 2020 10:55:23 +0200")

Juri Linkov <juri@linkov.net> writes:

>>> After Emacs 24.1, we should clean up the nobreak-char-display mechanism.
>>> The highlighted chars should be in a variable, not hardcoded.  The name
>>> `nobreak-char-display' should probably be changed.  Also, we should
>>> figure out how to deal with the different Unicode space characters.
>>
>> The latter was fixed earlier this year, I think?
>>
>> As for having the former in a variable -- is that warranted?  It would
>> mean slowing redisplay down a bit, I guess?  I don't know whether that's
>> worth it.
>>
>> Any opinions?
>
> To address specific needs for highlighting Unicode space characters,
> in bug#44236 I resorted to the GNU ELPA package 'markchars' that has
> the variable 'markchars-nobreak-space-pattern' with a list of
> Unicode space characters.

So if there's a package that does provide this functionality, then we
don't really need to have it in-core, either (since it doesn't seem like
this is a feature tons of people crave), and I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-12-08 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19  0:22 bug#9790: Cleaning up nobreak-char-display Chong Yidong
2020-12-07 17:38 ` Lars Ingebrigtsen
2020-12-08  8:55   ` Juri Linkov
2020-12-08 14:17     ` Lars Ingebrigtsen [this message]
2020-12-08 16:23     ` 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=87czzkjsa6.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=9790@debbugs.gnu.org \
    --cc=cyd@gnu.org \
    --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 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.