From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 59306@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#59306: 29.0.50; Resurrected bug?
Date: Sat, 19 Nov 2022 10:08:43 +0100 [thread overview]
Message-ID: <41389326-4D96-4CC6-8064-4EB99AFCEEE5@gmail.com> (raw)
In-Reply-To: <87wn7ra3bm.fsf@yahoo.com>
I think it’s solved!
/PA
PS:, dirty fit the late answer… life came in between…
Enviado desde mi iPhone
> El 19 nov 2022, a las 7:03, Po Lu <luangruo@yahoo.com> escribió:
>
> Po Lu <luangruo@yahoo.com> writes:
>
>> Dmitry Gutov <dgutov@yandex.ru> writes:
>>
>>> Since this bug sounds similar or at least related to bug#58912, I
>>> probably should comment:
>>>
>>> Rebuilding from the latest master makes the scenario in bug#58912 much
>>> better, in that the font size is applied correctly at the end.
>>>
>>> It's still different from Emacs 28 in that the frame size goes through
>>> an extra transition at the end of loading. And sometimes through 1
>>> more (the last one the same as the -2nd one). So sometimes I end up
>>> with a window of 84x37, and sometimes (less frequently) 80x35. All
>>> according to window-height and window-width.
>>>
>>> Emacs 28 and an older build of master both end up at 80x35.
>>>
>>> But at least the font size and family are ok now.
>>
>> I guess Cairo just refuses to tell us what the DPI it defaults to using
>> is, so Emacs always ends up having to redraw the fonts at startup.
>>
>> Please give me a while to think up a solution.
>
> Please see whether or not Emacs now behaves satisfactorily wrt this.
next prev parent reply other threads:[~2022-11-19 9:08 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41389326-4D96-4CC6-8064-4EB99AFCEEE5@gmail.com \
--to=paaguti@gmail.com \
--cc=59306@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).