From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 18637@debbugs.gnu.org
Subject: bug#18637: 24.4.50; doc of frame parameter DISPLAY vs actual value on MS Windows
Date: Mon, 06 Oct 2014 22:29:51 +0300 [thread overview]
Message-ID: <8361fxm1xs.fsf@gnu.org> (raw)
In-Reply-To: <c75b3094-d24b-4949-9c1e-b513c0b5bed7@default>
> Date: Mon, 6 Oct 2014 10:25:31 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 18637@debbugs.gnu.org
>
> > > Which function tells you what monitor is showing a given frame (on
> > > MS Windows)?
> >
> > frame-monitor-attributes, if I understand what you want.
>
> I see that that function returns some information about (attributes
> of) the monitor that is most associated with the argument frame. And
> I see that one of the attributes is `name'. Presumably, monitors
> would be distinguished by this parameter.
If you need to distinguish them, which should be very rarely.
> However, it is an optional parameter, so I can't imagine that one can
> count on it to distinguish monitors. (Just why is it optional?)
I guess it's optional because not all windowing systems support it.
It is always present on MS-Windows, AFAIK.
> If one cannot count on `name', how is the identity of monitors
> determined? Do you just go by the particular cons of attributes
> that is returned by `frame-monitor-attributes'?
Depends on what you need this for.
next prev parent reply other threads:[~2014-10-06 19:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<b5ac6ce3-5c0d-4517-a44f-6925cfccdcfd@default>
[not found] ` <<837g0dm95c.fsf@gnu.org>
2014-10-06 17:25 ` bug#18637: 24.4.50; doc of frame parameter DISPLAY vs actual value on MS Windows Drew Adams
2014-10-05 19:23 ` Drew Adams
2014-10-05 19:30 ` Eli Zaretskii
2014-10-05 19:44 ` Eli Zaretskii
2014-10-06 18:08 ` Andy Moreton
2014-10-06 18:23 ` Drew Adams
2014-10-07 18:35 ` Andy Moreton
2014-10-07 20:25 ` Drew Adams
2014-10-06 19:29 ` Eli Zaretskii [this message]
2014-10-06 20:52 ` Drew Adams
2014-10-07 15:14 ` Eli Zaretskii
[not found] <<c75b3094-d24b-4949-9c1e-b513c0b5bed7@default>
[not found] ` <<ce89167f-4906-496e-9ace-4d51e1741311@default>
[not found] ` <<83tx3flxn2.fsf@gnu.org>
2014-10-07 18:12 ` Drew Adams
2014-10-07 18:26 ` Eli Zaretskii
[not found] ` <<41484edb-9aaa-4f56-bf46-4ab70b609aac@default>
[not found] ` <<8361fvlos0.fsf@gnu.org>
2014-10-07 18:31 ` Drew Adams
[not found] <<b3d0f532-3b29-43d3-a41d-6687886307dc@default>
[not found] ` <<83ppe5mfed.fsf@gnu.org>
2014-10-06 16:31 ` Drew Adams
2014-10-06 16:54 ` Eli Zaretskii
[not found] <<12fc196e-cc82-4f22-8d2f-cede95542ea7@default>
[not found] ` <<83vbnymi0h.fsf@gnu.org>
[not found] ` <<83tx3imhdg.fsf@gnu.org>
2014-10-06 2:55 ` Drew Adams
2014-10-06 14:39 ` Eli Zaretskii
2014-10-06 16:34 ` Stefan Monnier
2014-10-06 2:55 ` Drew Adams
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=8361fxm1xs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18637@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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).