all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: alan@idiocy.org, 71866@debbugs.gnu.org
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	[thread overview]
Message-ID: <0acf5f45-27e1-43e7-8f3a-4631dd8d08b2@gutov.dev> (raw)
In-Reply-To: <9b9402cc-b5a2-435d-8307-f04ea0ffa69a@gutov.dev>

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	other threads:[~2024-07-24 20:08 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  3:14 bug#71866: 30.0.50; [macOS] Cursor hiding char behind it with certain theme customization Dmitry Gutov
2024-07-01 11:36 ` Eli Zaretskii
2024-07-02  1:07   ` Dmitry Gutov
2024-07-06  8:56     ` Eli Zaretskii
2024-07-09  2:37       ` Dmitry Gutov
2024-07-09 11:31         ` Eli Zaretskii
2024-07-10  2:46           ` Dmitry Gutov
2024-07-10 11:58             ` Eli Zaretskii
2024-07-19  1:57               ` Dmitry Gutov
2024-07-20  8:30                 ` Eli Zaretskii
2024-07-20 15:46                   ` Dmitry Gutov
2024-07-20 16:03                     ` Eli Zaretskii
2024-07-21  0:53                       ` Dmitry Gutov
2024-07-21  7:20                         ` Eli Zaretskii
2024-07-21  9:04                           ` Eli Zaretskii
2024-07-21 23:22                             ` Dmitry Gutov
2024-07-21 13:50                           ` Dmitry Gutov
2024-07-21 14:55                             ` Eli Zaretskii
2024-07-21 23:58                               ` Dmitry Gutov
2024-07-22 14:45                                 ` Eli Zaretskii
2024-07-22 15:27                                   ` Alan Third
2024-07-22 16:02                                     ` Alan Third
2024-07-23  1:11                                       ` Dmitry Gutov
2024-07-23 11:19                                         ` Eli Zaretskii
2024-07-24  0:48                                           ` Dmitry Gutov
2024-07-24 11:32                                             ` Eli Zaretskii
2024-07-24 14:34                                               ` Dmitry Gutov
2024-07-24 16:29                                                 ` Eli Zaretskii
2024-07-24 19:22                                                   ` Dmitry Gutov
2024-07-24 20:08                                                     ` Dmitry Gutov [this message]
2024-07-25  5:01                                                     ` Eli Zaretskii
2024-07-25 16:14                                                       ` Dmitry Gutov
2024-07-22 16:10                                     ` Eli Zaretskii
2024-07-22 19:02                                       ` Alan Third
2024-07-22 19:15                                         ` Eli Zaretskii
2024-07-22 19:47                                           ` Alan Third
2024-07-23  1:06                                   ` Dmitry Gutov
2024-07-23 11:17                                     ` Eli Zaretskii
2024-07-02 23:42 ` Stefan Kangas
2024-07-07  2:03   ` Dmitry Gutov
2024-07-09 18:22     ` Stefan Kangas
2024-07-10  2:56       ` Dmitry Gutov
2024-07-23  7:40         ` Gerd Möllmann
2024-07-24  0:56           ` Dmitry Gutov
2024-07-24  3:48             ` Gerd Möllmann
2024-07-24 19:16               ` Dmitry Gutov
2024-07-25  3:03                 ` Gerd Möllmann
2024-07-25  5:39                   ` Eli Zaretskii
2024-07-25  5:58                     ` Gerd Möllmann
2024-07-25 14:46                   ` Dmitry Gutov

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=0acf5f45-27e1-43e7-8f3a-4631dd8d08b2@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=71866@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --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.