From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 30074@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#30074: 26.0; Add function(s) for current monitor info
Date: Mon, 15 Jul 2019 09:17:42 -0700 (PDT) [thread overview]
Message-ID: <1a4b56c5-4238-4958-841f-fcf547a767d7@default> (raw)
In-Reply-To: <87pnmbcoak.fsf@mouse.gnus.org>
> > Yes, that takes care of the `current-monitor'
> > function, but not `current-monitor-size.
> > Please consider this bug report to be a
> > request for a function like that.
>
> Well, there's
> (x-display-pixel-width (selected-frame))
> => 1920
> (and height), so it seems like we're covered...
No, we're not covered. `C-h f x-display-pixel-width':
On "multi-monitor" setups this refers to the pixel width for all
physical monitors associated with DISPLAY. To get information for
each physical monitor, use 'display-monitor-attributes-list'.
IOW, use `display-monitor-attributes-list'.
I think you're missing the point of this
request. Yes, all such info is available
from `display-monitor-attributes-list'.
The point is to have specific functions
that provide it directly.
> And the function above also returns the same size data, but as an alist:
>
> (frame-monitor-attributes (selected-frame))
> => ((name . "eDP1") (geometry 0 0 1920 1080) (workarea 0 27 1920 1053) (mm-
> size 310 170) (frames #<frame movie.el 0x563f20223a30> #<frame emacs
> 0x563f22915f10>) (source . "Gdk"))
`current-monitor-size' is a convenience function.
Obviously you can get the info it provides by
digging it out of `display-monitor-attributes-list'
(or `frame-monitor-attributes', which just calls
`d-m-a-l').
`current-monitor-size' gives you directly,
au choix, the geometry or workarea size.
next prev parent reply other threads:[~2019-07-15 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 23:08 bug#30074: 26.0; Add function(s) for current monitor info Drew Adams
2019-07-14 17:46 ` Lars Ingebrigtsen
2019-07-14 19:49 ` Juri Linkov
2019-07-15 10:13 ` Lars Ingebrigtsen
2019-07-15 15:21 ` Drew Adams
2019-07-15 15:25 ` Lars Ingebrigtsen
2019-07-15 16:17 ` Drew Adams [this message]
2019-07-15 16:05 ` Andy Moreton
2019-07-15 16:24 ` Drew Adams
2019-07-15 16:35 ` Lars Ingebrigtsen
2019-07-15 16:42 ` Andy Moreton
2019-07-14 22:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1a4b56c5-4238-4958-841f-fcf547a767d7@default \
--to=drew.adams@oracle.com \
--cc=30074@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.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 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.