Re: Display of undisplayable characters: \U01F3A8 instead of diamond

[Emanuel Berg]

Gregory Heytings wrote:

> Here's a (real) story. A program for a certain task is
> awfully slow, it takes ten to fifteen minutes to finish that
> task, and the computer on which it runs becomes almost
> unusable during that time. It is made faster, and now takes
> at most a few seconds for that same task. Its end users are
> not at all happy with that improvement: they were
> comfortable with the slow program, because it was a good
> reason/excuse to take yet another break in their workday.

???

What does this refer to, did the method that showed the
diamonds in the Linux VTs do that for certain chars?

If so, I never experienced it, but good that you fixed
it obviously.

But please explain why is it so difficult to setup the mere
_interface_ aspect, which is the representation of
undisplayable chars, so that it can be configured to non-ASCII
chars as well?

  (setq undisplayable-char-char CHAR)

Char?

-- 
underground experts united
https://dataswamp.org/~incal