Re: [ottomaddox@fastmail.fm: emacsclient won't open new frame on remote display]

[Stefan Monnier <monnier@iro.umontreal.ca>]

> ***************
> *** 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