unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: wilnerthomas--- via "Emacs development discussions." <emacs-devel@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: Pascal Quesseveur <pquessev@gmail.com>, emacs-devel@gnu.org
Subject: Re: make-frame-command with multiple munitors
Date: Sat, 17 Sep 2022 20:37:30 +0200 (CEST)	[thread overview]
Message-ID: <NCBjQPb--3-2@tutanota.com> (raw)
In-Reply-To: <86o7vdc1f6.fsf@mail.linkov.net>


Sep 17, 2022, 17:55 by juri@linkov.net:

>> When I work with several monitors I would like that when, in a frame,
>> I run a command which opens a new frame, this frame is created on the
>> same monitor as that of the current frame, which is not always the
>> case.
>>
>> Function make-frame-on-current-monitor exists to meet this use case
>> but it is not really easy to use interactively. Variable
>> pop-up-frame-function can be set to use a function different from
>> make-frame for creating a new frame in display-buffer-pop-up-frame.
>>
>> I have used pop-up-frame-function to use make-frame-on-current-monitor
>> instead of make-frame. That works fine but there is no easy way to do
>> the same with special-display-popup-frame or make-frame-command.
>>
>> IMHO it would be worth to use such a variable in those functions too.
>>
>
> Sorry, the last line is unclear, please explain
> what variable and in what functions?
>
I wonder how can one pass a frame to a function that needs it as argument.

My frame reports as

 #<frame *scratch* - GNU Emacs at zeus 0x2c88d40>

And I want to call

(set-frame-position frame nlft ntop)







  reply	other threads:[~2022-09-17 18:37 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. [this message]
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
  -- 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=NCBjQPb--3-2@tutanota.com \
    --to=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=pquessev@gmail.com \
    --cc=wilnerthomas@tutanota.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).