all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gregory@heytings.org, stephen.berman@gmx.net,
	63271@debbugs.gnu.org, juri@linkov.net
Subject: bug#63271: 29.0.90; broken mouse-face
Date: Thu, 11 May 2023 14:23:58 +0800	[thread overview]
Message-ID: <87o7mrcrnl.fsf@yahoo.com> (raw)
In-Reply-To: <834joj76hg.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 11 May 2023 09:00:11 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Po Lu <luangruo@yahoo.com>
>> Cc: Gregory Heytings <gregory@heytings.org>,  juri@linkov.net,
>>   63271@debbugs.gnu.org,  stephen.berman@gmx.net
>> Date: Thu, 11 May 2023 08:51:05 +0800
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > Po Lu, was that change intentional?  If not, let's remove that line or
>> > move it under some conditional that doesn't include all Cairo builds.
>> > If it was intentional, please explain why, and let's take it from
>> > there.
>> 
>> It was needed to prevent drawing overhangs as part of the cursor from
>> overwriting surrounding characters with the glyph string background.
>> 
>> Unfortunately, I don't remember why it was needed, though I think the
>> underlying reason has been fixed.
>
> So can we undo that now?  If there is still a reason for doing
> something special there, it will pop up sooner or later, and we can
> deal with it at that time.  At the very least, the setting of
> s->background_filled_p should not be done when s->hl is one of the
> last 3 values in enum draw_glyphs_face, I think, and maybe also when
> s->for_overlaps is zero.
>
> I'd like to fix this soon, because I want to make another pretest of
> 29.1.

Yes, but please wait a day or two for me to get to a machine where I can
test this.  Thanks.





  reply	other threads:[~2023-05-11  6:23 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 15:11 bug#63271: 29.0.90; broken mouse-face Juri Linkov
2023-05-04 16:01 ` Eli Zaretskii
2023-05-05 17:38   ` Juri Linkov
2023-05-05 18:31     ` Eli Zaretskii
2023-05-06 11:19       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-07 18:00         ` Juri Linkov
2023-05-07 18:35           ` Eli Zaretskii
2023-05-08 15:56             ` Juri Linkov
2023-05-08 16:14               ` Eli Zaretskii
2023-05-08 18:20                 ` Stephen Berman
2023-05-08 18:27                   ` Eli Zaretskii
2023-05-08 18:47                     ` Stephen Berman
2023-05-08 19:09                       ` Juri Linkov
2023-05-08 20:46                         ` Stephen Berman
2023-05-09  6:47                           ` Juri Linkov
2023-05-09 19:06                             ` Juri Linkov
2023-05-09 19:21                               ` Eli Zaretskii
2023-05-09 23:19                                 ` Gregory Heytings
2023-05-10  9:38                                   ` Stephen Berman
2023-05-10 10:53                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-10 11:01                                       ` Stephen Berman
2023-05-10 12:05                                       ` Eli Zaretskii
2023-05-10 11:00                                   ` Eli Zaretskii
2023-05-11  0:51                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-11  6:00                                       ` Eli Zaretskii
2023-05-11  6:23                                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-05-12  3:19                                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-12 10:43                                           ` Eli Zaretskii
2023-05-12 12:49                                             ` Gregory Heytings
2023-05-12 17:20                                               ` Juri Linkov
2023-05-12 19:21                                                 ` Eli Zaretskii
2023-05-10  0:46                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-09  6:45                 ` Juri Linkov
2023-05-09  8:36                   ` Eli Zaretskii
2023-05-09  9:49                     ` Stephen Berman
2023-05-09 10:07                       ` Stephen Berman
2023-05-09 10:21                         ` Eli Zaretskii
2023-05-09 10:35                           ` Stephen Berman
2023-05-09 11:50                             ` Eli Zaretskii
2023-05-09 12:43                               ` Stephen Berman
2023-05-09 12:52                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-09 13:12                                   ` Stephen Berman
2023-05-09 13:35                                     ` Eli Zaretskii
2023-05-09 14:34                                       ` Stephen Berman
2023-05-10  0:34                                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-10  9:39                                           ` Stephen Berman
2023-05-09 13:32                                 ` Eli Zaretskii
2023-05-09 14:34                                   ` Stephen Berman
2023-05-10  0:47                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-09 10:14                       ` Eli Zaretskii
2023-05-09  1:08               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-09  6:43                 ` Juri Linkov
2023-05-09  8:43                   ` Eli Zaretskii
2023-05-09 11:44                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87o7mrcrnl.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=63271@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gregory@heytings.org \
    --cc=juri@linkov.net \
    --cc=luangruo@yahoo.com \
    --cc=stephen.berman@gmx.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.