From: Andrii Kolomoiets <andreyk.mad@gmail.com>
To: Christian Tietze <me@christiantietze.de>
Cc: 46406@debbugs.gnu.org
Subject: bug#46406: 28.0.50; [PATCH] Use frame monitor in frame_float
Date: Fri, 19 Feb 2021 12:07:32 +0200 [thread overview]
Message-ID: <m2tuq89xqz.fsf@gmail.com> (raw)
In-Reply-To: <m2y2fn9eg9.fsf@gmail.com> (Andrii Kolomoiets's message of "Wed, 17 Feb 2021 12:27:34 +0200")
Andrii Kolomoiets <andreyk.mad@gmail.com> writes:
> Christian Tietze <me@christiantietze.de> writes:
>
>> Hi Andrii,
>
> Hi Christian
>
>> Your Emacs patch for (non)retina screens and frame sizes introduced a
>> very weird bug where on the non-retina screen, the contents of the
>> frame are drawn in 1/4th the available drawing space. It looks fine on
>> the retina screen, though.
>>
>> See screenshots:
>> https://github.com/daviderestivo/homebrew-emacs-head/issues/92
>>
>> I cannot offer a fix suggestion for this, because I don't know the
>> emacs source well. Maybe you know something from the top of your head?
>
> I'll take a look.
With the commit 0e2b123a4ef600f5b337972a7bb61c1fc4b7d0cd I have no
issue moving frame to the non-retina screen. The issue appears for me
with the commit 68bd6f3ea9c05637501139c46f1f4304482db95f.
I suspect your issue were introduced in Bug#46155
next prev parent reply other threads:[~2021-02-19 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1v9arf7nl.fsf@christiantietze.de>
2021-02-17 10:27 ` bug#46406: 28.0.50; [PATCH] Use frame monitor in frame_float Andrii Kolomoiets
2021-02-19 10:07 ` Andrii Kolomoiets [this message]
2021-02-19 13:04 ` Lars Ingebrigtsen
2021-02-19 19:38 ` Alan Third
2021-02-20 13:00 ` Lars Ingebrigtsen
2021-02-22 22:08 ` Christian Tietze
2021-02-22 22:11 ` Lars Ingebrigtsen
2021-02-09 17:46 Andrii Kolomoiets
2021-02-11 9:10 ` Lars Ingebrigtsen
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=m2tuq89xqz.fsf@gmail.com \
--to=andreyk.mad@gmail.com \
--cc=46406@debbugs.gnu.org \
--cc=me@christiantietze.de \
/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.