From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Third Newsgroups: gmane.emacs.devel Subject: Re: dpyinfo Date: Thu, 10 Dec 2020 19:48:56 +0000 Message-ID: References: <83sg8d4vc4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21629"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 10 20:50:39 2020 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 1knRxX-0005YD-Mu for ged-emacs-devel@m.gmane-mx.org; Thu, 10 Dec 2020 20:50:39 +0100 Original-Received: from localhost ([::1]:37748 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1knRxW-00083P-No for ged-emacs-devel@m.gmane-mx.org; Thu, 10 Dec 2020 14:50:38 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60190) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knRwD-0007Bd-E7 for emacs-devel@gnu.org; Thu, 10 Dec 2020 14:49:17 -0500 Original-Received: from outbound.soverin.net ([2a01:4f8:fff0:2d:8::218]:38555) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knRvy-0001Ma-Up; Thu, 10 Dec 2020 14:49:16 -0500 Original-Received: from smtp.soverin.net (unknown [10.10.3.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id C696C60233; Thu, 10 Dec 2020 19:48:59 +0000 (UTC) Original-Received: from smtp.soverin.net (smtp.soverin.net [159.69.232.142]) by soverin.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=idiocy.org; s=soverin; t=1607629739; bh=kLte+siMFxjkkFrwDJZhAUOfRRrs3Aj53PZcAitO21Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=DBKTBM9EzmNbbB4fdqW7X89k+g1/MTDJQ67J7cQEvn9H5u35eOtm8YKQn1I+3FGEs 8AJJdxkkJsk1T0cTwctQp1BDiYOofcnDWT9lXjaXV6weMwUSnasd83s0zZdAIC273S MljRZSKZa9VgRaRapl+9xz7BxjeXrYNhq9dOUIknHhjO42zaskuDbZ3jTh8ZHoNmkX uYk2XCfBlh83gDezxzzCf3/9oYkOUvNZMUpn2F/4fFS2F+6m87HssaKEISP5qrZxU0 Qkf4fKLjdvqU+/AE+9E0npKM4WFN2Zbd0d5IfJNEH6ZOkyPA15ThJjLY3sWQiVkzLj hf4Lgbts3PBlg== Original-Received: by breton.holly.idiocy.org (Postfix, from userid 501) id 4342620286C1E0; Thu, 10 Dec 2020 19:48:56 +0000 (GMT) Mail-Followup-To: Alan Third , Eli Zaretskii , emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: <83sg8d4vc4.fsf@gnu.org> Received-SPF: pass client-ip=2a01:4f8:fff0:2d:8::218; envelope-from=alan@idiocy.org; helo=outbound.soverin.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:260666 Archived-At: On Thu, Dec 10, 2020 at 03:57:47PM +0200, Eli Zaretskii wrote: > > Date: Wed, 9 Dec 2020 21:55:56 +0000 > > From: Alan Third > > > > I've been looking at using the screen's actual DPI setting when > > generating SVG files for bug 45124 and I was wondering if the dpyinfo > > struct is updated as the frame moves from screen to screen? My guess > > is that it's not, and it's only set when the frame is created? > > The resolution is set in init_xterm, so I'd expect it to be run > whenever a new display is open, not when a frame is created. What > happens when one moves from one screen to another, I don't know, but > if they are on the same X display, the resolution indeed doesn't > change, AFAICT. Thanks for confirming what I thought. -- Alan Third