all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Juri Linkov <juri@linkov.net>
Cc: luangruo@yahoo.com, Eli Zaretskii <eliz@gnu.org>, 63271@debbugs.gnu.org
Subject: bug#63271: 29.0.90; broken mouse-face
Date: Mon, 08 May 2023 22:46:49 +0200	[thread overview]
Message-ID: <87h6smh7pi.fsf@gmx.net> (raw)
In-Reply-To: <86r0rqfxnn.fsf@mail.linkov.net> (Juri Linkov's message of "Mon,  08 May 2023 22:09:16 +0300")

On Mon, 08 May 2023 22:09:16 +0300 Juri Linkov <juri@linkov.net> wrote:

>>> mouse-face specifies only the background color, so I'm at a loss how
>>> could a font affect that.  There's something I'm missing here.  Like
>>> some corruption of the realized faces or something.
>>>
>>> Do you see the same in Emacs 28 and 27?  If some older version doesn't
>>> show this, any chance of bisecting it?
>>
>> I cannot reproduce the problematic display in Emacs 28.  I'll see if I
>> can bisect, but it may take a while.
>
> I tried to bisect and see the problem in
>
> 61b9f2c3179..: 2022-11-17 * lisp/emacs-lisp/shortdoc.el (sequence): Don't use
> cl-lib (bug#59319)
>
> but not in
>
> 0636e1066bb..: 2022-11-16 ; Don't unnecessarily use non-ASCII characters in Texinfo

I checked out those commits and rebuilt emacs and can confirm that the
build from 61b9f2c3179 has the problem and the build from 0636e1066bb
does not.

> probably because 61b9f2c3179 is the last commit of a big merge at that time.

If I'm not misreading the vc-change-log, it looks like that commit is
from Stefan's merge of the noverlay branch, and it seems not implausible
that some change in that branch is the source of the problem.  (But my
git skills are elementary, so I may well be misreading it.)  Is it
possible to confine bisection to the commits from a merge, and if so,
how?

Steve Berman





  reply	other threads:[~2023-05-08 20:46 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 [this message]
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
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=87h6smh7pi.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=63271@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    --cc=luangruo@yahoo.com \
    /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.