From: Christopher Dimech <dimech@gmx.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Pascal Quesseveur <pquessev@gmail.com>,
emacs-devel@gnu.org, juri@linkov.net
Subject: Re: make-frame-command with multiple munitors
Date: Mon, 19 Sep 2022 15:21:11 +0200 [thread overview]
Message-ID: <trinity-4b549d39-03f3-46ea-94dd-b322bdb2015e-1663593671152@3c-app-mailcom-bs10> (raw)
In-Reply-To: <87a66vo8eb.fsf@yahoo.com>
> Sent: Tuesday, September 20, 2022 at 12:28 AM
> 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
>
> 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.
Emacs has the capability of placing a frame at some position. It is then
logical for emacs to look into the monitor configuration to determine the
current monitor (then placing at corners or center oy monitor). It would
a feature very much appreciated if made to happen.
> 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.
>
next prev parent reply other threads:[~2022-09-19 13:21 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
2022-09-19 13:21 ` Christopher Dimech [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-4b549d39-03f3-46ea-94dd-b322bdb2015e-1663593671152@3c-app-mailcom-bs10 \
--to=dimech@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=luangruo@yahoo.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.