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: Dmitry Gutov <dgutov@yandex.ru>
Cc: 59306@debbugs.gnu.org, Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Subject: bug#59306: 29.0.50; Resurrected bug?
Date: Mon, 21 Nov 2022 08:34:49 +0800	[thread overview]
Message-ID: <87sfid6t7a.fsf@yahoo.com> (raw)
In-Reply-To: <3d6e6d77-c5cd-35b9-5f3b-4ec9d6d7db92@yandex.ru> (Dmitry Gutov's message of "Sun, 20 Nov 2022 18:47:32 +0200")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 20.11.2022 02:36, Po Lu via Bug reports for GNU Emacs, the Swiss
> army knife of text editors wrote:
>> Dmitry Gutov<dgutov@yandex.ru>  writes:
>> 
>>> No change since the last test I tried: fonts seem fine, but the frame
>>> size is jumping. I even did 'make bootstrap' to be doubly sure.
>> Thanks.  Could you place a breakpoint on `apply_xft_settings' before
>> starting "emacs -Q", step through it, and try to find out what causes
>> the `changed' variable to be set to true?
>
> Apparently it's this part:
>
> #ifdef FC_HINT_STYLE
>   if ((settings->seen & SEEN_HINTSTYLE) != 0
>       && oldsettings.hintstyle != settings->hintstyle)
>     {
>       FcPatternDel (pat, FC_HINT_STYLE);
>       FcPatternAddInteger (pat, FC_HINT_STYLE, settings->hintstyle);
>       changed = true;
>       oldsettings.hintstyle = settings->hintstyle;
>     }
> #endif
>
> Here's the relevant part of the gdb log, since I don't have much
> experience with it. The assignment statement itself seems to be
> missing from the stepping, but 'changed' became true after:
>
> (gdb) n
> 842       FcPatternGetDouble (pat, FC_DPI, 0, &oldsettings.dpi);
> (gdb) p changed
> $2 = false
> (gdb) n
> 844       if ((settings->seen & SEEN_AA) != 0 && oldsettings.aa !=
> settings->aa)
> (gdb) n
> 852       if ((settings->seen & SEEN_HINTING) != 0
> (gdb) n
> 860       if ((settings->seen & SEEN_RGBA) != 0 && oldsettings.rgba !=
> settings->rgba)
> (gdb) n
> 869       if ((settings->seen & SEEN_LCDFILTER) != 0
> (gdb) n
> 879       if ((settings->seen & SEEN_HINTSTYLE) != 0
> (gdb) n
> 882           FcPatternDel (pat, FC_HINT_STYLE);
> (gdb) n
> 883           FcPatternAddInteger (pat, FC_HINT_STYLE, settings->hintstyle);
> (gdb) n
> 885           oldsettings.hintstyle = settings->hintstyle;
> (gdb) n
> 894       oldsettings.dpi = dpyinfo->resx;
> (gdb) p changed
> $3 = true

Thanks.  That's quite annoying, I guess Cairo isn't reporting the
default hint style to us either.

I can't think of a good solution off-hand, please give me some more
time.





  reply	other threads:[~2022-11-21  0:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 11:49 bug#59306: 29.0.50; Resurrected bug? Pedro Andres Aranda Gutierrez
2022-11-16 13:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17  1:28   ` Dmitry Gutov
2022-11-17  2:10     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-19  6:03       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-19  9:08         ` Pedro Andres Aranda Gutierrez
2022-11-19 10:03           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-19 14:06             ` Dmitry Gutov
2022-11-20  0:36               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-20 16:47                 ` Dmitry Gutov
2022-11-21  0:34                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-25  8:28                     ` Pedro Andres Aranda Gutierrez
2022-11-25  9:11                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-25 16:09                         ` Pedro Andres Aranda Gutierrez
2022-11-17  6:22     ` Pedro Andres Aranda Gutierrez

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=87sfid6t7a.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59306@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=luangruo@yahoo.com \
    --cc=paaguti@gmail.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.