From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 21173@debbugs.gnu.org
Subject: bug#21173: 25.0.50; New frames positioned off screen with multiple monitors
Date: Wed, 28 Oct 2015 20:08:05 +0200 [thread overview]
Message-ID: <83k2q63lyy.fsf@gnu.org> (raw)
In-Reply-To: <vz1h9laj46s.fsf@gmail.com>
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Wed, 28 Oct 2015 17:25:31 +0000
>
> > To see the difference, you need a test case where the selected frame
> > and the frame used in your code are different.
>
> Please suggest a suitable test case. The patch fixed the original bug,
> and has not caused me any problems in daily usage.
Indeed, I missed the fact that this code is only interested in the
"display", not the frame. And the w32 build of Emacs only supports a
single display, so the frame indeed doesn't matter. Which means you
could invoke Fw32_display_monitor_attributes_list with the argument of
Qnil, and still get the same effect.
Sorry for the noise.
next prev parent reply other threads:[~2015-10-28 18:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 3:28 bug#21173: 25.0.50; New frames positioned off screen with multiple monitors Francis Litterio
2015-08-01 10:51 ` martin rudalics
2015-08-01 15:03 ` Francis Litterio
2015-08-01 15:49 ` martin rudalics
2015-08-01 16:59 ` Francis Litterio
2015-08-03 6:47 ` martin rudalics
2015-08-03 20:35 ` Andy Moreton
2015-08-03 21:12 ` Glenn Morris
2015-08-04 16:31 ` Fran Litterio
2015-09-08 22:26 ` Andy Moreton
2015-10-06 7:57 ` martin rudalics
2015-10-07 16:50 ` Fran
2015-10-21 18:57 ` Francis Litterio
2015-10-21 23:37 ` Andy Moreton
2015-10-22 6:39 ` martin rudalics
2015-10-27 21:53 ` Andy Moreton
2015-10-28 9:55 ` martin rudalics
2015-10-28 14:13 ` Andy Moreton
2015-10-28 15:52 ` Eli Zaretskii
2015-10-28 17:25 ` Andy Moreton
2015-10-28 18:08 ` Eli Zaretskii [this message]
2015-10-28 19:21 ` martin rudalics
2015-10-28 19:39 ` Andy Moreton
2015-10-29 7:57 ` 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=83k2q63lyy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21173@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.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.