unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: make-frame-command with multiple munitors
Date: Wed, 21 Sep 2022 13:44:59 +0800	[thread overview]
Message-ID: <878rmdi8mc.fsf@yahoo.com> (raw)
In-Reply-To: <CAO48Bk8SvOGwKpbO5+UngDN+t__qgDUwFXPsWEO=aXtonG78HA@mail.gmail.com> (Pedro Andres Aranda Gutierrez's message of "Wed, 21 Sep 2022 07:22:36 +0200")

Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:

> OK... a longer answer ;-) the moment you include (top . xxx) or (left
> . xxx) in the (default|init)-frame-alist the vales are taken as
> absolute values in the window manager's space, and Emacs will be
> placed (normally) somewhere in the display that is designated as 0
> (the Linux laptop or MacBook Pro) independently of which display you
> were when you lunched Emacs.

Well yes, that's intentional behavior.  Setting `top' or `left' tells
the window manager to try very hard to place the frame at the specified
location on the screen.  If you want the frame to be placed at the
correct location, you will have to either remove both position
parameters from initial-frame-alist, for it to be positioned by the WM,
or manually specify the position of the monitor you want.

A note about terminology from the POV of Emacs: the normal coordinate
space of a connection to the X server (the connection is referred to as
a "display") is relative to the root window of the display's default
screen.  A screen is then split into different "monitors", which are
potentially overlapping rectangular subsets of the screen's root window,
normally displayed in a single physical monitor, not counting overscan
or underscan.

`top' and `left' coordinates are specified relative to the root window
of the screen, not "in the display that is designated to 0", nor is such
a coordinate system affected by the monitor in which the initial frame
was created.  Where in the root window coordinate system individual
monitors are placed can only be determined by the output of
display-monitor-attributes-list.



  reply	other threads:[~2022-09-21  5:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20  9:35 Re: Re: make-frame-command with multiple munitors Pedro Andres Aranda Gutierrez
2022-09-20 10:14 ` Emanuel Berg
2022-09-20 11:07 ` Po Lu
2022-09-20 14:37   ` Pedro Andres Aranda Gutierrez
2022-09-21  2:15     ` Po Lu
2022-09-21  5:08       ` Pedro Andres Aranda Gutierrez
2022-09-21  5:22         ` Pedro Andres Aranda Gutierrez
2022-09-21  5:44           ` Po Lu [this message]
2022-09-21  9:21             ` Pedro Andres Aranda Gutierrez
2022-09-21 10:52               ` Po Lu
2022-09-21 10:55                 ` Pedro Andres Aranda Gutierrez
2022-09-21 11:44                   ` Po Lu
  -- strict thread matches above, loose matches on Subject: below --
2022-09-15 15:15 Pascal Quesseveur
2022-09-17 17:55 ` Juri Linkov
2022-09-17 18:37   ` wilnerthomas--- via Emacs development discussions.
2022-09-19  7:21   ` Pascal Quesseveur
2022-09-19 12:28     ` Po Lu
2022-09-19 13:21       ` Christopher Dimech
2022-09-19 13:38         ` Po Lu
2022-09-19 14:54           ` Christopher Dimech
2022-09-19 17:58       ` Pascal Quesseveur
2022-09-19 19:22         ` Juri Linkov
2022-09-20  6:57           ` Juri Linkov
2022-09-19 20:16         ` Christopher Dimech

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=878rmdi8mc.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=paaguti@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).