From: Andy Moreton <andrewjmoreton@gmail.com>
To: 34516@debbugs.gnu.org
Subject: bug#34516: Multi-monitor frame sets
Date: Wed, 20 Feb 2019 21:38:02 +0000 [thread overview]
Message-ID: <vz1r2c25ef9.fsf@gmail.com> (raw)
In-Reply-To: <87bm3a74s4.fsf@mail.linkov.net>
On Wed 20 Feb 2019, Juri Linkov wrote:
>> (display-monitor-attributes-list)
>> ;; ==>
>> '(((geometry 0 0 1920 1080)
>> (workarea 0 0 1920 1050)
>> (mm-size 677 381)
>> (name . "\\\\.\\DISPLAY1")
>> (frames ...))
>> ((geometry -1680 -1050 1680 1050)
>> (workarea -1680 -1050 1680 1050)
>> (mm-size 593 370)
>> (name . "\\\\.\\DISPLAY2")
>> (frames ...)))
>
> I see that ‘geometry’ is the same as ‘workarea’ on the second monitor,
> but slightly different on the first one. Mine are all the same,
> so I don't know whether to use ‘geometry’ or ‘workarea’.
In the example above, the DISPLAY1 monitor has the Windows task bar
along the bottom edge (with auto-hide disabled), so space there is not
available for displaying emacs frames.
The Windows task bar is not displayed on the DISPLAY2 monitor in this
setup, so the DISPLAY2 workarea matches the geometry, as the whole
monitor can be used to display frames.
You should always use the workarea values for displaying emacs frames.
AndyM
next prev parent reply other threads:[~2019-02-20 21:38 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
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 [this message]
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=vz1r2c25ef9.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=34516@debbugs.gnu.org \
/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).