From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: uzibalqa Newsgroups: gmane.emacs.help Subject: Re: Frame shifted upwards upon changing font size Date: Wed, 14 Sep 2022 15:07:07 +0000 Message-ID: References: <87k066z1r2.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31349"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Gregory Heytings , Eli Zaretskii , help-gnu-emacs@gnu.org To: Po Lu Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 14 17:08:45 2022 Return-path: Envelope-to: geh-help-gnu-emacs@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 1oYU0L-00081G-0W for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 14 Sep 2022 17:08:45 +0200 Original-Received: from localhost ([::1]:37478 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYU0K-0000BD-1N for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 14 Sep 2022 11:08:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38422) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYTzB-0000Ah-O2 for help-gnu-emacs@gnu.org; Wed, 14 Sep 2022 11:07:33 -0400 Original-Received: from mail-4318.protonmail.ch ([185.70.43.18]:25273) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYTz7-0002jW-Ms; Wed, 14 Sep 2022 11:07:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1663168045; x=1663427245; bh=vcFkx63Q2kGp3pQ/gsaVFyqGIcu1MNcFoBSDrmVAcmY=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=J1IGehWS3KCLm3a0dm04u9fOiWeAv1eaI7hK1ka4KtLNvxyureEFuapsyowvqb2vx LTOBWVEV/S5PPx581MM5UrDYbhcglumrnlUvd/TU8UvG6xD9yaLllRrukNzp8ReDzG AXsA68akLkWZYnwz4q/cMLig8tiYQ0HWocAc76E9tFu/u88pvPRKHTU6PGbhLPhgAq doTH1sEnsn7TlL7K+2Lmdrt3KB15D5o77frlVhOFaQD3aebWu9/SPJ3leMQF/EM2Zn vJH+PSx2Gj/rnUau+CmIUCzfzfgUTQaHPUIDBmLPZdWcSDkB2j22nzRsHttj8hQSrS 5WsPt62Bh0Ddg== In-Reply-To: <87k066z1r2.fsf@yahoo.com> Feedback-ID: 52887082:user:proton Received-SPF: pass client-ip=185.70.43.18; envelope-from=uzibalqa@proton.me; helo=mail-4318.protonmail.ch 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:139459 Archived-At: ------- Original Message ------- On Wednesday, September 14th, 2022 at 10:30 AM, Po Lu = wrote: > uzibalqa uzibalqa@proton.me writes: >=20 > > Could emacs get to understand the monitor within which the initial fram= e > > gets displayed and be able to center the frame in that monitor? >=20 >=20 > That gets tricky very quickly. Monitor names are not guaranteed to > remain unique, and X-level identifiers are reused in a monotonically > increasing fashion and cannot be relied on to uniquely identify the > monitor on which where the initial frame was created. >=20 > In fact, X has 3 kinds of "monitor": CRTCs, outputs, and monitors. A > CRT controller defines a rectangle in the screen that has a single mode > line, and can have multiple outputs attached. An output is a physical > output that displays the contents of its CRTC, and a monitor is a subset > of the screen that represents a non-disjoint collection of pixels that > will be presented to the user through 1 or more outputs, which may be > connected to any number of CRTCs. >=20 > Of course, a frame might be displayed in multiple overlapping monitors, > outputs, and CRT controllers, at any given time. >=20 > Under such a situation, where do you propose to center the frame? In the middle of the monitor defined by the location of the mouse pointer, = perhaps.