From: Emanuel Berg <incal@dataswamp.org>
To: emacs-tangents@gnu.org
Subject: Re: Display of undisplayable characters: \U01F3A8 instead of diamond
Date: Fri, 02 Sep 2022 23:13:43 +0200 [thread overview]
Message-ID: <87y1v1xywo.fsf@dataswamp.org> (raw)
In-Reply-To: 2f302d1c39aad333be6d@heytings.org
Gregory Heytings wrote:
>>> I understand (academically) that once someone has adapted
>>> themselves to a particular set of bugs, shortcomings, and
>>> limitations
>>
>> But here the bug was actually better from our perspective ...
>
> In which case you still have at least two possibilities:
>
> 1. Use an earlier version of Emacs in which that bug
> is present.
>
> 2. Build your own patched Emacs in which that bug
> is restored.
With this
(set-char-table-extra-slot glyphless-char-display 0 "%")
and the latest change to not get the brackets for a single
char its pretty equivalent but the diamond was slightly better
since the percent sign (%) is a common char that is used not
all the time maybe but often enough. The with the yellow face
it isn't a problem, really.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-09-02 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1oRQ6X-0007In-OK@fencepost.gnu.org>
[not found] ` <87edx28cl1.fsf@disroot.org>
[not found] ` <E1oSVZB-0008Vf-1X@fencepost.gnu.org>
[not found] ` <83y1v7w6eu.fsf@gnu.org>
[not found] ` <E1oSsba-00065k-NL@fencepost.gnu.org>
[not found] ` <dacea928880b805d23c2@heytings.org>
[not found] ` <E1oTtfF-0001PX-2x@fencepost.gnu.org>
[not found] ` <2f302d1c3966849477b3@heytings.org>
[not found] ` <YxHlIPwwApfe5fuk@ACM>
[not found] ` <83mtbiovzr.fsf@gnu.org>
[not found] ` <YxIHp5P8sBRjz/Vg@ACM>
[not found] ` <83a67hq3l7.fsf@gnu.org>
2022-09-02 14:39 ` Display of undisplayable characters: \U01F3A8 instead of diamond chad
2022-09-02 14:42 ` Gregory Heytings
2022-09-02 18:49 ` Emanuel Berg
2022-09-02 19:41 ` Gregory Heytings
2022-09-02 21:13 ` Emanuel Berg [this message]
2022-09-02 20:39 ` chad
2022-09-02 21:14 ` Emanuel Berg
2022-09-02 21:52 ` Alan Mackenzie
2022-09-03 0:33 ` Gregory Heytings
2022-09-03 1:41 ` Emanuel Berg
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=87y1v1xywo.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-tangents@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.
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).