From: martin rudalics <rudalics@gmx.at>
To: "Charles A. Roelli" <charles@aurox.ch>, 25818@debbugs.gnu.org
Subject: bug#25818: 25.2; frame moved off display does not return (OS X)
Date: Thu, 23 Feb 2017 09:49:54 +0100 [thread overview]
Message-ID: <58AEA232.4000708@gmx.at> (raw)
In-Reply-To: <m2bmtw632t.fsf@aurox.ch>
> You can evaluate this code from emacs -Q to have a frame gradually moved
> in steps of 200 px from position ((top . 1) (left . 1)) until it's just
> past the right edge of the display (more or less), and then come back
> again:
...
> On GNU/Linux and MS Windows the frame behaves as expected: when the
> frame parameters are changed to bring it back onscreen (step 2), the
> frame becomes visible again. On OS X 10.6 the frame stays off screen,
> however, and I can't find any way to put it back on screen. You can
> change the frame parameters for `top' and `left', and they'll stick, but
> they don't actually seem to have any effect.
>
> Can someone reproduce this on a more recent OS X? Maybe the problem is
> fixed in newer versions.
FWIW this seems OS X specific behavior. Compare
http://superuser.com/questions/55341/move-an-off-screen-window-back-on-screen-on-mac-os-x
http://osxdaily.com/2013/08/14/move-window-back-on-screen-mac-os-x/
http://www.gottabemobile.com/how-to-move-an-os-x-window-thats-stuck-off-screen/
http://apple.stackexchange.com/questions/709/how-to-retrieve-windows-that-have-moved-off-screen
https://www.cnet.com/forums/discussions/bring-misplaced-off-screen-applications-back-to-your-desktop-380285/
martin
next prev parent reply other threads:[~2017-02-23 8:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 20:04 bug#25818: 25.2; frame moved off display does not return (OS X) Charles A. Roelli
2017-02-23 8:49 ` martin rudalics [this message]
2017-02-26 11:26 ` Charles A. Roelli
2017-02-26 15:40 ` Charles A. Roelli
2017-02-26 16:45 ` martin rudalics
2017-02-26 19:42 ` Charles A. Roelli
2017-02-27 8:05 ` martin rudalics
2017-02-27 10:34 ` Charles A. Roelli
2017-02-27 20:47 ` Charles A. Roelli
2017-02-28 10:12 ` Charles A. Roelli
2017-02-28 13:20 ` Anders Lindgren
2017-02-28 15:05 ` Charles A. Roelli
2017-02-28 20:35 ` Anders Lindgren
2017-02-28 22:05 ` Drew Adams
2017-03-01 10:48 ` Anders Lindgren
2017-03-01 16:10 ` Drew Adams
2017-03-19 19:38 ` Charles A. Roelli
2017-03-27 18:22 ` Anders Lindgren
2017-04-02 14:14 ` Charles A. Roelli
2017-04-03 8:33 ` Anders Lindgren
2017-04-08 20:40 ` Charles A. Roelli
2017-04-09 19:13 ` Anders Lindgren
2017-04-10 19:54 ` Charles A. Roelli
2017-04-11 18:35 ` Anders Lindgren
2017-04-27 19:14 ` Charles A. Roelli
2017-04-27 20:05 ` Alan Third
2017-04-28 17:33 ` Charles A. Roelli
2017-05-02 20:33 ` Alan Third
2017-05-05 18:30 ` Charles A. Roelli
2017-04-29 10:30 ` martin rudalics
2017-04-29 11:15 ` Charles A. Roelli
2017-04-29 14:51 ` Alan Third
2017-04-29 17:23 ` Anders Lindgren
2017-04-30 8:32 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58AEA232.4000708@gmx.at \
--to=rudalics@gmx.at \
--cc=25818@debbugs.gnu.org \
--cc=charles@aurox.ch \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).