unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Andy Moreton <andrewjmoreton@gmail.com>, 30074@debbugs.gnu.org
Subject: bug#30074: 26.0; Add function(s) for current monitor info
Date: Mon, 15 Jul 2019 09:24:33 -0700 (PDT)	[thread overview]
Message-ID: <098a0314-8c32-4535-8976-96e27a54af36@default> (raw)
In-Reply-To: <vz1y30zmgf0.fsf@gmail.com>

> > Please consider this bug report to be a
> > request for a function like [`current-monitor-size'].
> 
> Doesn't the returned monitor attributes list give you that information ?

Yes, and the bug report made that clear from the
beginning (with `display-monitor-attributes-list').

> (frame-monitor-attributes (selected-frame))
> => ((geometry 0 0 1920 1080)...)
> 
> What other information do you need ?

It's not about _needing other information_.
It's about having a function that gives you
the size info directly.

This is getting a bit ridiculous.  Why do
you think we have functions like this?

(defun frame-width (&optional frame)
  "Return number of columns available for display on FRAME.
If FRAME is omitted, describe the currently selected frame."
  (cdr (assq 'width (frame-parameters frame))))

Why don't you complain that `frame-parameters'
already gives you that information? "What other
information do you need?"





  reply	other threads:[~2019-07-15 16:24 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
2019-07-15 16:05         ` Andy Moreton
2019-07-15 16:24           ` Drew Adams [this message]
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=098a0314-8c32-4535-8976-96e27a54af36@default \
    --to=drew.adams@oracle.com \
    --cc=30074@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).