From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: 30074@debbugs.gnu.org
Subject: bug#30074: 26.0; Add function(s) for current monitor info
Date: Mon, 15 Jul 2019 12:13:57 +0200 [thread overview]
Message-ID: <m3d0ib38re.fsf@gnus.org> (raw)
In-Reply-To: <87muhgtn0c.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 14 Jul 2019 22:49:23 +0300")
Juri Linkov <juri@linkov.net> writes:
>>> Please consider adding a function that returns the info describing the
>>> monitor that dominates a frame (default: selected frame). In
>>> particular, the size of the monitor. This can be useful, for example,
>>> for positioning a frame when there are multiple monitors.
>>>
>>> I've been using this, but you might have a better implementation in
>>> mind:
>>>
>>> (defun current-monitor (&optional frame)
>>> "Attributes of monitor that dominates FRAME (default: `selected-frame')."
>>> (catch 'current-monitor
>>> (dolist (atts (display-monitor-attributes-list frame))
>>> (when (member (or frame (selected-frame)) (cdr (assq 'frames atts)))
>>> (throw 'current-monitor atts)))
>>> nil)) ; Should never happen (?)
>>
>> I guess it's possible for a frame to be on several monitors? (Half on
>> one and half on another.) What would this function return in that case?
>
> There is already `frame-monitor-attributes' added in Emacs 24 (see NEWS.24),
> e.g.
>
> (frame-monitor-attributes (selected-frame))
So there is. Drew, does this function do what you want?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-15 10:13 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 [this message]
2019-07-15 15:21 ` Drew Adams
2019-07-15 15:25 ` Lars Ingebrigtsen
2019-07-15 16:17 ` Drew Adams
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
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=m3d0ib38re.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=30074@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).