From: martin rudalics <rudalics@gmx.at>
To: chad <yandros@mit.edu>, EMACS development team <emacs-devel@gnu.org>
Subject: Re: Odd resizing behavior on git HEAD
Date: Tue, 12 Apr 2022 09:44:24 +0200 [thread overview]
Message-ID: <13262414-3618-d64f-e5f2-aa397f7be03d@gmx.at> (raw)
In-Reply-To: <CAO2hHWaqxEJASrpwq-jdjdoCVcXmT_XJOhiD0zjr5m=r69ahWw@mail.gmail.com>
> For the past week or so, I've noticed a change of behavior for emacs
> frames: when I create a new frame, it appears at the default size and
> location, as normal. If I then move and resize it using the window systems
> "snap to side" functionality (that is, I drag the window from the titlebar
> to the edge of the display, the window manager shows me a preview of the
> window full-height and half-screen width, placed on that edge), and then
> release it. Until sometime a week or two ago, the frame was correctly moved
> and resized; today (and for a fews days, at least), its upper-right corner
> is placed in the same position as before, but the size is unchanged. If I
> repeat the operation a second time, the window is placed in the same
> position, but this time it *is* resized.
>
> It's possible that this change is due to an os/window system change, but
> that would require some very coincidental timing.
>
> Has anyone else noticed a change similar to this? My current window system
> is unusual (x display via xwayland under chromeos), but the previous
> behavior has been stable for at least a couple years.
If this is as easy to reproduce as you sketched above, then my first
suggestion is to bisect master until you find a corresponding change.
martin
next prev parent reply other threads:[~2022-04-12 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 19:27 Odd resizing behavior on git HEAD chad
2022-04-12 0:38 ` Po Lu
2022-04-12 7:44 ` martin rudalics [this message]
2022-04-12 20:18 ` chad
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=13262414-3618-d64f-e5f2-aa397f7be03d@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=yandros@mit.edu \
/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.