From: Juri Linkov <juri@linkov.net>
To: Pascal Quesseveur <pquessev@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: make-frame-command with multiple munitors
Date: Tue, 20 Sep 2022 09:57:08 +0300 [thread overview]
Message-ID: <86r106pm7v.fsf@mail.linkov.net> (raw)
In-Reply-To: <86v8pj2nn0.fsf@mail.linkov.net> (Juri Linkov's message of "Mon, 19 Sep 2022 22:22:43 +0300")
>> Or maybe these functions could also use , but
>> that doesn't seem to be what was intended.
>
> It seems the default behavior of make-frame-command can't be changed,
> as well as the default value of pop-up-frame-function.
I recall seeing a variable like 'make-frame-function',
but now can't find it. Such a variable could help you
to replace its default value 'make-frame' with
customized value 'make-frame-on-current-monitor'.
This requires changing all current calls of
'make-frame' to (funcall 'make-frame-function).
next prev parent reply other threads:[~2022-09-20 6:57 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
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 [this message]
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=86r106pm7v.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=emacs-devel@gnu.org \
--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).