unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Po Lu <luangruo@yahoo.com>
Cc: Gregory Heytings <gregory@heytings.org>,
	Eli Zaretskii <eliz@gnu.org>,
	help-gnu-emacs@gnu.org
Subject: Re: Frame shifted upwards upon changing font size
Date: Wed, 14 Sep 2022 15:07:07 +0000	[thread overview]
Message-ID: <OUoLkj_AOmkNH3eXKrrcGfv-8wWSNPLni-Ta6opycFLq34b9ffs-ejgPICZn0w9Om5wzO7xGtBuJsDFyKsvwKk7hC8XFxJkz8p4InPFfHYc=@proton.me> (raw)
In-Reply-To: <87k066z1r2.fsf@yahoo.com>


------- Original Message -------
On Wednesday, September 14th, 2022 at 10:30 AM, Po Lu <luangruo@yahoo.com> wrote:


> uzibalqa uzibalqa@proton.me writes:
> 
> > Could emacs get to understand the monitor within which the initial frame
> > gets displayed and be able to center the frame in that monitor?
> 
> 
> 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.
> 
> 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.
> 
> Of course, a frame might be displayed in multiple overlapping monitors,
> outputs, and CRT controllers, at any given time.
> 
> 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.




  reply	other threads:[~2022-09-14 15:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  4:27 Frame shifted upwards upon changing font size uzibalqa
2022-09-13 11:29 ` Eli Zaretskii
2022-09-13 12:10   ` uzibalqa
2022-09-13 12:25     ` uzibalqa
2022-09-13 13:22       ` Gregory Heytings
2022-09-13 13:45         ` uzibalqa
2022-09-13 13:53           ` Gregory Heytings
2022-09-13 13:57             ` uzibalqa
2022-09-13 15:28               ` Gregory Heytings
2022-09-13 21:07                 ` uzibalqa
2022-09-14 10:10                   ` Robert Pluim
2022-09-14 15:09                     ` uzibalqa
2022-09-15  7:17                       ` Robert Pluim
2022-09-15 11:43                         ` uzibalqa
2022-09-15 12:25                           ` Robert Pluim
2022-09-15 13:38                             ` Po Lu
2022-09-15 15:09                           ` Pascal Quesseveur
2022-09-15 16:07                             ` Yuri Khan
2022-09-15 16:27                               ` Pascal Quesseveur
2022-09-14 10:30                   ` Po Lu
2022-09-14 15:07                     ` uzibalqa [this message]
2022-09-14 15:21                     ` Christopher Dimech
2022-09-13 12:29     ` Eli Zaretskii
2022-09-13 12:40       ` uzibalqa
2022-09-13 13:03         ` Eli Zaretskii
2022-09-13 13:15           ` uzibalqa

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='OUoLkj_AOmkNH3eXKrrcGfv-8wWSNPLni-Ta6opycFLq34b9ffs-ejgPICZn0w9Om5wzO7xGtBuJsDFyKsvwKk7hC8XFxJkz8p4InPFfHYc=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=eliz@gnu.org \
    --cc=gregory@heytings.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=luangruo@yahoo.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.
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).