From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: ***SPAM*** Re: (x-display-pixel-height) Date: Sat, 21 May 2022 11:33:24 +0300 Message-ID: <8335h39tez.fsf@gnu.org> References: <9A8CEE6D-D021-4B40-8130-C89F51A98F51@easesoftware.com> <87leuyl4ax.fsf@yahoo.com> <7B1F4496-3539-4C6D-8470-C08A18022F10@easesoftware.com> <87sfp5ypxl.fsf@yahoo.com> <87ilpzvfdw.fsf@yahoo.com> <87wneftvwp.fsf@yahoo.com> <837d6f9v3z.fsf@gnu.org> <87o7zrthss.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40237"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 21 10:37:25 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nsKc0-000AMM-PM for ged-emacs-devel@m.gmane-mx.org; Sat, 21 May 2022 10:37:24 +0200 Original-Received: from localhost ([::1]:51274 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nsKbz-00018L-9J for ged-emacs-devel@m.gmane-mx.org; Sat, 21 May 2022 04:37:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52352) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nsKYK-0007GT-F8 for emacs-devel@gnu.org; Sat, 21 May 2022 04:33:37 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49076) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nsKYI-0003gE-Bb; Sat, 21 May 2022 04:33:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Dy4dqWrgpYTtfY2U3+zuEg98hgzmt2jexwXsdSSd2F4=; b=HN11wHYblVnp 2J6wDIJrS4P7SqEGT1qbwnWe3MwxPEvHDe/cH7lTEwdr4lnhztECn0D8uefLXBgba6rww09p1Lbnj uijrBVpTuNtU13KUiigFE1xWYmYJ+gszPTsDldIcypFkbx85zAZe3hRd6gYb/gxRpRI8DoW4l/LNn m5gAvp+XJcv4EFa5AMvC88N45YJWObxfPqwhKay/2cHsoN+PSNo8G7f6Lz095h6whZcSJFD2YHw6S zyR5MbBq2lS6c9F+UprLdGJ8KWVbLrDz7QVE0VbSUx5llAbxaHlua98g4xNiHSk4F2kfNmUMSJjrZ eyTBC3eVusRv5BuWNETHQA==; Original-Received: from [87.69.77.57] (port=4871 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nsKYG-0006e8-N8; Sat, 21 May 2022 04:33:33 -0400 In-Reply-To: <87o7zrthss.fsf@yahoo.com> (message from Po Lu on Sat, 21 May 2022 16:24:03 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:290038 Archived-At: > From: Po Lu > Cc: emacs-devel@gnu.org > Date: Sat, 21 May 2022 16:24:03 +0800 > > > This doesn't give any hints for how should a Lisp program get the > > information about the monitor-configuration changes that triggered the > > hook call, given just the terminal name. Without knowing how to > > access that information, this hook is not very useful. > > That information isn't available in sufficient detail inside the events > that we get from the window system. The idea is that programs will call > `display-monitor-attributes-list' to retrieve the new monitor > configuration, which is always available after the hook is run. > > How about this? > > @cindex monitor change functions > @defvar display-monitors-changed-functions > This variable is an abnormal hook run when the monitor configuration > changes, which can happen if a monitor is rotated, moved, added or > removed from a multiple-monitor setup, if the primary monitor changes, > or if the resolution of a monitor changes. It is called with a single > argument consisting of the terminal on which the monitor configuration > changed. Programs should call @code{display-monitor-attributes-list} > with the terminal as the argument to retrieve the changed monitor > configuration inside this hook. > @end defvar This is okay, but please say "to retrieve the new configuration on that terminal" instead of a more vague "to retrieve the changed monitor configuration". > > I also notice that this hook was implemented for all the supported GUI > > backends except w32, which is unfortunate and undocumented. > > I plan to try implementing it there in the coming days. TIA.