From: martin rudalics <rudalics@gmx.at>
To: Alex <agrambot@gmail.com>
Cc: 23568@debbugs.gnu.org
Subject: bug#23568: 25.0.94; Mode line menus appear incorrectly in some monitor configurations
Date: Fri, 02 Jun 2017 11:00:56 +0200 [thread overview]
Message-ID: <59312948.5000907@gmx.at> (raw)
In-Reply-To: <8737bi97s9.fsf@gmail.com>
> In the end, we would still leave the function interface so that users
> can still call the discussed procedures from lisp code, right?
I think so, yes.
> (defun display-monitor-attribute (attribute &optional frame x y)
> "Return the value of the attribute of the 'current' monitor.
> By default, use the frame info to determine the current monitor,
> but if x and y are non-nil then use the given coordinates to
> determine it."
> (if (and x y)
Probably, FRAME should be replaced by DISPLAY as in other ‘display-...’
functions. X and Y must be checked properly to avoid throwing an error
when they are used in the arithmetics. And the doc-string should
explicitly state that the first argument is ignored when X and Y are
both non-nil.
martin
next prev parent reply other threads:[~2017-06-02 9:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 20:44 bug#23568: 25.0.94; Mode line menus appear incorrectly in some monitor configurations Alex
2016-05-18 21:28 ` Alex
2017-05-28 7:09 ` Alex
2017-05-31 7:14 ` Alex
2017-05-31 9:26 ` martin rudalics
2017-05-31 21:18 ` Alex
2017-06-01 5:39 ` martin rudalics
2017-06-01 20:33 ` Alex
2017-06-01 20:51 ` Alex
2017-06-02 6:10 ` martin rudalics
2017-06-02 7:18 ` Alex
2017-06-02 9:00 ` martin rudalics [this message]
2017-06-03 0:54 ` Alex
2017-06-03 6:32 ` Eli Zaretskii
2017-06-03 19:19 ` Alex
2017-06-04 14:28 ` Eli Zaretskii
2017-06-05 8:03 ` Alex
2017-06-05 15:36 ` Eli Zaretskii
2017-06-05 19:33 ` martin rudalics
2017-06-10 9:30 ` Eli Zaretskii
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=59312948.5000907@gmx.at \
--to=rudalics@gmx.at \
--cc=23568@debbugs.gnu.org \
--cc=agrambot@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 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.