From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [ottomaddox@fastmail.fm: emacsclient won't open new frame on remote display] Date: Thu, 06 Jul 2006 18:14:07 -0400 Message-ID: References: <873bdhdt2z.fsf@stupidchicken.com> <87hd1w8a3e.fsf@stupidchicken.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1152224063 17065 80.91.229.2 (6 Jul 2006 22:14:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 6 Jul 2006 22:14:23 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 07 00:14:21 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Fyc6x-0007Kf-7o for ged-emacs-devel@m.gmane.org; Fri, 07 Jul 2006 00:14:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fyc6w-0000PL-Gw for ged-emacs-devel@m.gmane.org; Thu, 06 Jul 2006 18:14:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fyc6j-0000OF-69 for emacs-devel@gnu.org; Thu, 06 Jul 2006 18:14:01 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fyc6g-0000KM-IN for emacs-devel@gnu.org; Thu, 06 Jul 2006 18:14:00 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fyc6g-0000KF-AG for emacs-devel@gnu.org; Thu, 06 Jul 2006 18:13:58 -0400 Original-Received: from [209.226.175.93] (helo=tomts36-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fyc6x-00026x-EV for emacs-devel@gnu.org; Thu, 06 Jul 2006 18:14:15 -0400 Original-Received: from localhost ([70.55.80.219]) by tomts36-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060706221357.BLGS13653.tomts36-srv.bellnexxia.net@localhost>; Thu, 6 Jul 2006 18:13:57 -0400 Original-Received: by localhost (Postfix, from userid 20848) id 7B7D38CDE; Thu, 6 Jul 2006 18:14:07 -0400 (EDT) Original-To: Chong Yidong In-Reply-To: <87hd1w8a3e.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 05 Jul 2006 09:17:25 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:56669 Archived-At: >> 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. > As the original bug report indicates, the current default behavior is > that the buffer is not displayed at all, which is clearly broken. My > thinking is that it makes more sense to create the new frame, to > ensure that the default behavior (with no customizations) works. If > the user customizes the emacsserver behavior, like changing it to use > pop-to-buffer, those personal customizations can be adapted to work > with extra displays. But the default behavior must definitely work. > What do you think? The OP's problem is indeed clearly a bug. I was just pointing out why your patch is not a good fix. Stefan