From: Robert Pluim <rpluim@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 31920@debbugs.gnu.org,
Jonathan Kyle Mitchell <kyle@jonathanmitchell.org>
Subject: bug#31920: 26.1; frame appears in wrong part of desktop after restoring frameset from fullscreen
Date: Wed, 27 Jun 2018 11:07:20 +0200 [thread overview]
Message-ID: <87woukpph3.fsf@gmail.com> (raw)
In-Reply-To: <5B2E0779.4080201@gmx.at> (martin rudalics's message of "Sat, 23 Jun 2018 10:40:25 +0200")
martin rudalics <rudalics@gmx.at> writes:
> I found a simpler scenario: With emacs -Q do C-x r f a, drag the frame
> somewhere else on your screen and do C-x r j a. Here the registered
> position is restored. Now do C-x r f a, drag the frame somewhere
> else, do F11 and C-x r j a. Here the frame is restored to the
> position it had before F11 and not to the one registered by C-x r f a.
>
I confirm this exact behaviour under GTK.
> So this time it seems that I have the right explanation: We first
> position the frame according to the position from the register and
> then demaximize it. But we should first demaximize and then
> reposition it. Can you confirm?
That looks like it. The patch I sent earlier fixes it for me, but Iʼm
not sure itʼs the right solution, it feels very heavyweight.
Robert
next prev parent reply other threads:[~2018-06-27 9:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 3:12 bug#31920: 26.1; frame appears in wrong part of desktop after restoring frameset from fullscreen Jonathan Kyle Mitchell
2018-06-21 7:16 ` martin rudalics
2018-06-21 10:25 ` Robert Pluim
2018-06-22 8:55 ` martin rudalics
2018-06-22 11:19 ` Robert Pluim
2018-06-22 12:17 ` martin rudalics
2018-06-22 13:50 ` Robert Pluim
2018-06-23 8:40 ` martin rudalics
2018-06-27 9:07 ` Robert Pluim [this message]
2018-06-28 8:03 ` martin rudalics
2019-07-01 6:08 ` Spenser Truex
2018-06-21 15:54 ` Eli Zaretskii
2018-06-22 8:55 ` 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=87woukpph3.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=31920@debbugs.gnu.org \
--cc=kyle@jonathanmitchell.org \
--cc=rudalics@gmx.at \
/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.