From: martin rudalics <rudalics@gmx.at>
To: emacs-devel <emacs-devel@gnu.org>
Cc: Alan Third <alan@idiocy.org>, Yuuki Harano <masm+emacs@masm11.me>
Subject: Re: Proposing changes to adjust_frame_size
Date: Tue, 27 Apr 2021 10:22:47 +0200 [thread overview]
Message-ID: <e0ff8bfd-f2d0-56d7-953b-ca0fee1356da@gmx.at> (raw)
In-Reply-To: <93687325-1196-f83a-e6c0-44a5ec624868@gmx.at>
> Unless there are objections, I intend to apply the attached changes in
> the next days. Their purpose is to restrain the handling of the text
> area size of a frame to the function adjust_frame_size and have the
> various front/backends setting frame sizes or receiving notifications
> about them work with native frame sizes only. This has the advantage
> that storing the history of frame size changes and consequently tracking
> bugs in the frame sizing code become much simpler.
>
> The patch should fix Bug#46827 and I intend to add further bug fixes in
> the following days. Some of these fixes are controversial and I'd like
> to push them separately in order to make bisecting easier. Other than
> that, there should be no user noticeable changes, so if you observe any
> strange frame sizing behavior, please tell me.
>
> I've tested the patch with xfwm4, gnome shell, kde plasma and Windows XP
> but have given it only light testing with GNUstep. Alan, if you see
> anything fishy with the NS build, please tell me. Yuuki, if you see any
> problems with the pgtk build, please tell me too so we can resolve them
> without causing greater conflicts.
Done. If frames resize strangely now, please complain immediately.
Thanks, martin
next prev parent reply other threads:[~2021-04-27 8:22 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 17:11 Proposing changes to adjust_frame_size martin rudalics
2021-04-27 8:22 ` martin rudalics [this message]
2021-04-27 14:16 ` Yuuki Harano
2021-05-02 8:46 ` martin rudalics
2021-05-02 11:21 ` Alan Third
2021-05-02 16:17 ` martin rudalics
2021-05-05 8:51 ` martin rudalics
2021-05-05 10:47 ` Yuuki Harano
2021-05-05 11:24 ` martin rudalics
2021-05-05 14:07 ` Yuuki Harano
2021-05-05 15:01 ` martin rudalics
2021-05-05 16:45 ` martin rudalics
2021-05-05 18:54 ` Tassilo Horn
2021-05-06 7:44 ` martin rudalics
2021-05-06 7:59 ` Tassilo Horn
2021-05-06 8:39 ` martin rudalics
2021-05-06 8:49 ` Tassilo Horn
2021-05-06 12:10 ` martin rudalics
2021-05-06 12:31 ` Tassilo Horn
2021-05-06 14:10 ` martin rudalics
2021-05-06 14:47 ` Tassilo Horn
2021-05-07 8:03 ` martin rudalics
2021-05-08 7:02 ` Tassilo Horn
2021-05-08 7:16 ` martin rudalics
2021-05-08 14:03 ` Tassilo Horn
2021-05-08 15:17 ` martin rudalics
2021-05-08 20:32 ` Tassilo Horn
2021-05-09 8:41 ` martin rudalics
2021-05-09 10:09 ` Garjola Dindi
2021-05-09 10:12 ` Garjola Dindi
2021-05-09 18:48 ` Tassilo Horn
2021-05-10 8:25 ` martin rudalics
2021-05-10 12:27 ` martin rudalics
2021-05-10 19:05 ` Tassilo Horn
2021-05-10 19:21 ` martin rudalics
2021-05-10 19:28 ` Tassilo Horn
2021-05-11 8:29 ` martin rudalics
2021-05-11 9:25 ` Tassilo Horn
2021-05-12 8:44 ` martin rudalics
2021-05-12 14:53 ` Tassilo Horn
2021-05-12 16:40 ` martin rudalics
2021-05-12 19:06 ` Tassilo Horn
2021-05-13 7:55 ` martin rudalics
2021-05-13 8:08 ` Tassilo Horn
2021-05-16 8:29 ` martin rudalics
2021-05-16 8:33 ` Tassilo Horn
2021-05-16 9:14 ` martin rudalics
2021-05-16 9:16 ` Tassilo Horn
2021-05-16 12:24 ` martin rudalics
2021-05-16 19:08 ` Tassilo Horn
2021-05-17 7:33 ` martin rudalics
2021-05-06 14:41 ` Yuuki Harano
2021-05-09 9:32 ` Yuuki Harano
2021-05-09 13:47 ` martin rudalics
2021-05-09 15:30 ` Yuuki Harano
2021-05-10 8:24 ` martin rudalics
2021-05-10 13:18 ` Yuuki Harano
2021-05-10 14:16 ` martin rudalics
2021-05-10 15:41 ` Yuuki Harano
2021-05-10 19:20 ` martin rudalics
2021-05-11 14:32 ` Yuuki Harano
2021-05-12 8:47 ` martin rudalics
2021-05-13 8:48 ` Garjola Dindi
2021-05-01 18:59 ` Alan Third
2021-05-02 7:38 ` martin rudalics
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=e0ff8bfd-f2d0-56d7-953b-ca0fee1356da@gmx.at \
--to=rudalics@gmx.at \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=masm+emacs@masm11.me \
/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.