From: Alan Third <alan@idiocy.org>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: 40200@debbugs.gnu.org, HaiJun Zhang <netjune@outlook.com>,
Andrii Kolomoiets <andreyk.mad@gmail.com>
Subject: bug#40200: bug#28872: [PATCH v4] Fix NS frame resizing issues (bug#40200, bug#28872)
Date: Sun, 3 May 2020 19:41:44 +0100 [thread overview]
Message-ID: <20200503184144.GB24860@breton.holly.idiocy.org> (raw)
In-Reply-To: <m2r1w1t000.fsf@fastmail.fm>
On Sun, May 03, 2020 at 08:13:35PM +0300, Filipp Gunbin wrote:
> Hi, I've just filed bug#41055 which is also about NS frame resizing, it
> may have something to do with this...
Does this patch make any difference to your issue? Or is it the cause?
Most likely the commit that’s broken it is
24cb6908d70c14792c686679cb08091447b9c3b1
--
Alan Third
next prev parent reply other threads:[~2020-05-03 18:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 18:13 bug#40200: 28.0.50; NS: text drawing glitches in maximized frame with frame-inhibit-implied-resize Andrii Kolomoiets
2020-03-23 19:22 ` Eli Zaretskii
2020-03-23 19:47 ` Andrii Kolomoiets
2020-03-23 23:54 ` Alan Third
2020-03-25 22:28 ` bug#40200: [PATCH] Fix NS frame resizing issues (bug#40200, bug#28872) Alan Third
2020-03-26 17:35 ` bug#28872: " Andrii Kolomoiets
2020-03-26 21:21 ` bug#28872: [PATCH v2] " Alan Third
2020-03-27 9:45 ` Andrii Kolomoiets
2020-03-27 13:22 ` Andrii Kolomoiets
2020-03-28 1:56 ` Alan Third
2020-04-04 14:17 ` bug#40200: [PATCH v3] " Alan Third
2020-04-06 6:57 ` Andrii Kolomoiets
2020-04-06 18:44 ` bug#28872: [PATCH v4] " Alan Third
2020-04-07 8:14 ` bug#40200: " Andrii Kolomoiets
2020-04-16 18:24 ` bug#28872: " Alan Third
2020-04-18 1:52 ` bug#40200: " HaiJun Zhang
2020-04-18 12:07 ` Alan Third
2020-04-18 14:12 ` HaiJun Zhang
2020-04-18 15:26 ` Alan Third
2020-04-19 1:49 ` HaiJun Zhang
2020-05-03 16:26 ` Alan Third
2020-05-03 17:13 ` Filipp Gunbin
2020-05-03 18:41 ` Alan Third [this message]
2020-05-03 19:49 ` Filipp Gunbin
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=20200503184144.GB24860@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=40200@debbugs.gnu.org \
--cc=andreyk.mad@gmail.com \
--cc=fgunbin@fastmail.fm \
--cc=netjune@outlook.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.