unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Pascal Quesseveur <pquessev@gmail.com>
Cc: emacs-devel@gnu.org,  juri@linkov.net
Subject: Re: make-frame-command with multiple munitors
Date: Mon, 19 Sep 2022 20:28:44 +0800	[thread overview]
Message-ID: <87a66vo8eb.fsf@yahoo.com> (raw)
In-Reply-To: <82pmfr25iu.fsf@gmail.com> (Pascal Quesseveur's message of "Mon,  19 Sep 2022 09:21:45 +0200")

Pascal Quesseveur <pquessev@gmail.com> writes:

> I imagine there's a reason make-frame-on-current-monitor didn't
> outright replace make-frame (personally it seems more normal to me to
> always open a new frame on the current monitor, but I can imagine
> that this is not the general case.)

Because opening a frame on the right monitor is the job of the window
manager, not Emacs.

Notice how make-frame-on-current-monitor always sets the "user specified
position" flag in the window manager hints property.  The window manager
will then blindly obey the initial position (0, 0 from the origin of the
monitor) instead of placing the window in the right monitor while also
taking into account window placement constraints and policy.



  reply	other threads:[~2022-09-19 12:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 15:15 make-frame-command with multiple munitors 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2022-09-20  9:35 Re: " 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
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

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=87a66vo8eb.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=pquessev@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).