bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#71866: 30.0.50; [macOS] Cursor hiding char behind it with certain th


From: Dmitry Gutov
Subject: bug#71866: 30.0.50; [macOS] Cursor hiding char behind it with certain theme customization
Date: Wed, 24 Jul 2024 23:08:25 +0300
User-agent: Mozilla Thunderbird

On 24/07/2024 22:22, Dmitry Gutov wrote:
On 24/07/2024 19:29, Eli Zaretskii wrote:
Date: Wed, 24 Jul 2024 17:34:18 +0300
Cc: alan@idiocy.org, 71866@debbugs.gnu.org
From: Dmitry Gutov <dmitry@gutov.dev>

Then I don't understand what you mean by "many/most characters become
blank under cursor".  It seems to contradict what you say now: that
"only one char is blanked".

In the recipe I managed to produce starting with 'emacs -Q', only 's' is
such a character (see the original description). When point is over 'a'
or 'd', no bug.

In actual practice, many/all characters exhibit the problem, I just
haven't managed to create a simple repro for this.

Curiouser and curiouser.  And when you say that 's' is a character
that is blanked, does it mean that if you have several such
characters, then moving the cursor to any of them will show the
problem?

Yes: with buffer contents 'asdasdasdasd' (or any small variations of that), only the 's' chars exhibit the problem with the repro script.

With my custom init, all of the chars exhibit the problem.

I don't understand even in principle how a display problem could be
specific to some characters, unless it's something related very
strongly to the font that is being used.  So what happens in a session
in which 's' is a problematic character if you put a face property on
's' that forces Emacs to use a different font?

I tried something different: enabled variable-pitch-mode.

* With the small repro script in the first message, the problem is gone.

* With my custom init, the problem remains for all chars. *shrug*

OTOH, for example

 (put-text-property (point) (1+ (point) 'font-lock-face '(:family "Arial"))

doesn't have that effect (when point is at one of the 's'-es) - the bug's still there.

A couple of more experiments:

- Buffer text 'asdasdasdasdsssssssss' - the problem occurs only on at the first 3 's'-es.

- Buffer text 'asdasdasdasdaaaaaaaaa' - the problem occurs at positions

2, 5, 8, 11 and [14..] - that is, the first 3 's'-es, and then for all 'a'-s at the end except the first one (that comes after the last 'd').





reply via email to

[Prev in Thread] Current Thread [Next in Thread]