From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [ottomaddox@fastmail.fm: emacsclient won't open new frame on remote display]
Date: Tue, 04 Jul 2006 17:04:03 -0400 [thread overview]
Message-ID: <jwvu05xcchq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <873bdhdt2z.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 04 Jul 2006 16:16:04 -0400")
> ***************
> *** 207,220 ****
> ;; and select it.
> (unless (equal (frame-parameter (selected-frame) 'display) display)
> (select-frame
> ! (make-frame-on-display
> ! display
> ! ;; This frame is only there in place of an actual "current display"
> ! ;; setting, so we want it to be as unobtrusive as possible. That's
> ! ;; what the invisibility is for. The minibuffer setting is so that
> ! ;; we don't end up displaying a buffer in it (which noone would
> ! ;; notice).
> ! '((visibility . nil) (minibuffer . only)))))))
> (defun server-unquote-arg (arg)
> (replace-regexp-in-string
> --- 207,213 ----
> ;; and select it.
> (unless (equal (frame-parameter (selected-frame) 'display) display)
> (select-frame
> ! (make-frame-on-display display)))))
> (defun server-unquote-arg (arg)
> (replace-regexp-in-string
This suggested change causes Emacs to create a new frame displaying some
random buffer. If server.el subsequently uses switch-to-buffer or something
like that, it's probably OK, but if it instead uses something like
pop-to-buffer because you want to display emacsclient buffers in their own
window or frame, then you end up with 2 windows (or frames) one of which
displays some random buffer.
Stefan
next prev parent reply other threads:[~2006-07-04 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 17:25 [ottomaddox@fastmail.fm: emacsclient won't open new frame on remote display] Richard Stallman
2006-07-04 20:16 ` Chong Yidong
2006-07-04 21:04 ` Stefan Monnier [this message]
2006-07-05 13:17 ` Chong Yidong
2006-07-06 22:14 ` Stefan Monnier
2006-07-06 22:49 ` Chong Yidong
2006-07-07 15:21 ` Stefan Monnier
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=jwvu05xcchq.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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).