GNU bug report logs - #34516
Multi-monitor frame sets

Previous Next

Full log

View this message in rfc822 format

From: Andy Moreton <andrewjmoreton <at> gmail.com>
To: 34516 <at> debbugs.gnu.org
Subject: bug#34516: Multi-monitor frame sets
Date: Wed, 20 Feb 2019 21:38:02 +0000

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.