From: Juri Linkov <juri@linkov.net>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 34516-done@debbugs.gnu.org
Subject: bug#34516: Multi-monitor frame sets
Date: Mon, 25 Feb 2019 23:11:47 +0200 [thread overview]
Message-ID: <875zt7efos.fsf@mail.linkov.net> (raw)
In-Reply-To: <864l8srg4f.fsf@gmail.com> (Andy Moreton's message of "Sun, 24 Feb 2019 22:11:44 +0000")
>>>> Since on Windows 'display-monitor-attributes-list' returns such
>>>> fake monitor names:
>>>>
>>>> \\.\DISPLAY1
>>>> \\.\DISPLAY2
>>>>
>>>> on macOS it could return something like that or generate fake names
>>>> from geometry like "1920x1080+0+0", "2560x1440+1920+16".
>>>
>>> I often have two identical monitors attached, so that would be
>>> confusing :-)
>>>
>>> Something like this (assuming nobody every connects more than 9
>>> monitors to the same system).
>>
>> I hope at least the primary monitor always comes first in the list.
>
> The `display-monitor-attributes-list' docstring states:
>
> "Return a list of physical monitor attributes on DISPLAY.
> DISPLAY can be a display name, a terminal name, or a frame.
> If DISPLAY is omitted or nil, it defaults to the selected frame’s display.
> Each element of the list represents the attributes of a physical
> monitor. The first element corresponds to the primary monitor."
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Why are you still guessing, instead of reading the documentation ?
Right, the documentation should be the ultimate source of truth.
So I committed the patch to master.
next prev parent reply other threads:[~2019-02-25 21:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 19:34 bug#34516: Multi-monitor frame sets Juri Linkov
2019-02-18 10:47 ` Robert Pluim
2019-02-18 21:03 ` Juri Linkov
2019-02-19 9:17 ` Robert Pluim
2019-02-23 20:43 ` Juri Linkov
2019-02-24 12:56 ` Robert Pluim
2019-02-24 21:08 ` Juri Linkov
2019-02-24 22:11 ` Andy Moreton
2019-02-25 21:11 ` Juri Linkov [this message]
2019-03-02 20:54 ` Alan Third
2019-03-02 23:57 ` Andy Moreton
2019-03-03 11:43 ` Alan Third
2019-03-04 9:52 ` Robert Pluim
2019-03-04 13:56 ` Andy Moreton
2019-03-04 16:10 ` Robert Pluim
2019-03-04 19:20 ` Alan Third
2019-03-04 20:18 ` Robert Pluim
2019-03-19 21:33 ` Juri Linkov
2019-03-26 7:24 ` Robert Pluim
2019-03-26 7:26 ` Robert Pluim
2019-03-27 21:46 ` Juri Linkov
2019-03-28 7:56 ` Robert Pluim
2019-03-28 21:57 ` Juri Linkov
2019-02-18 16:48 ` Eli Zaretskii
2019-02-18 21:16 ` Juri Linkov
2019-02-19 3:32 ` Eli Zaretskii
2019-02-19 21:37 ` Juri Linkov
2019-02-19 10:40 ` Andy Moreton
2019-02-19 21:31 ` Juri Linkov
2019-02-19 23:29 ` Andy Moreton
2019-02-20 21:20 ` Juri Linkov
2019-02-20 21:38 ` Andy Moreton
2019-02-23 20:48 ` Juri Linkov
2019-02-24 8:44 ` martin rudalics
2019-02-24 21:08 ` Juri Linkov
2019-02-24 22:13 ` Andy Moreton
2019-02-25 10:13 ` martin rudalics
2019-02-25 15:00 ` Andy Moreton
2019-03-05 0:44 ` Andy Moreton
2019-03-29 8:16 ` Robert Pluim
2019-03-30 21:47 ` Juri Linkov
2019-04-01 11:29 ` Robert Pluim
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=875zt7efos.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=34516-done@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 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).