From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: Pretest? Date: Wed, 14 Mar 2007 09:56:08 -0400 Message-ID: <87hcso2akn.fsf@stupidchicken.com> References: <87slcf8qxr.fsf@stupidchicken.com> <20070309135920.GA3560@kobe.laptop> <87hcsuwk6w.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1173880615 613 80.91.229.12 (14 Mar 2007 13:56:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 14 Mar 2007 13:56:55 +0000 (UTC) Cc: Juanma Barranquero , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 14 14:56:37 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HRTy0-0003dK-UU for ged-emacs-devel@m.gmane.org; Wed, 14 Mar 2007 14:56:37 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HRTyt-0000Av-W9 for ged-emacs-devel@m.gmane.org; Wed, 14 Mar 2007 08:57:32 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HRTyq-00007R-1D for emacs-devel@gnu.org; Wed, 14 Mar 2007 09:57:28 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HRTyp-00006H-8F for emacs-devel@gnu.org; Wed, 14 Mar 2007 08:57:27 -0500 Original-Received: from south-station-annex.mit.edu ([18.72.1.2]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HRTxv-00025x-Lx; Wed, 14 Mar 2007 09:56:31 -0400 Original-Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82]) by south-station-annex.mit.edu (8.13.6/8.9.2) with ESMTP id l2EDuSLB010726; Wed, 14 Mar 2007 08:56:29 -0500 (EST) Original-Received: from outgoing-legacy.mit.edu (OUTGOING-LEGACY.MIT.EDU [18.7.22.104]) by grand-central-station.mit.edu (8.13.6/8.9.2) with ESMTP id l2EDuESW012159; Wed, 14 Mar 2007 09:56:14 -0400 (EDT) Original-Received: from localhost (SYDNEYPACIFIC-SEVEN-THIRTY-FOUR.MIT.EDU [18.95.7.223]) ) by outgoing-legacy.mit.edu (8.13.6/8.12.4) with ESMTP id l2EDuDww013172; Wed, 14 Mar 2007 09:56:14 -0400 (EDT) Original-Received: from cyd by localhost with local (Exim 3.36 #1 (Debian)) id 1HRTxY-0001Tf-00; Wed, 14 Mar 2007 09:56:08 -0400 In-Reply-To: (Richard Stallman's message of "Tue\, 13 Mar 2007 23\:24\:21 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.95 (gnu/linux) X-Scanned-By: MIMEDefang 2.42 X-Spam-Score: -2.599 X-detected-kernel: Solaris 9.1 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:67930 Archived-At: Richard Stallman writes: > > I think that in cases like this server.el should display the new buffer > > in another window, so that the user knows to go over and edit it. > > If the user wants server.el to display emacsclient-sent buffers in > another window or frame, he can set server-window. > > Yes, but that is a different issue. I am talking about what to do > when emacsclient wants to display a buffer, but something like a > minibuffer or an isearch prevents it from switching effectively to > that buffer in the normal way. > > It should display that buffer in another window, and not abort > anything. That might means the new buffer will not be immediately available for editing, until the user cancels the minibuffer or isearch. If the user calls emacsclient, the intention is almost certainly to perform the edit in Emacs, so this is a minor nuisance. Another possible complication (which I haven't thought much about) is when Emacs has frames open on more than one display. If you are currently working on one display, having left isearch on in another display, invoking emacsclient might lead to puzzling behavior. Anyway, I don't feel strongly about this issue one way or another. As Juanma has said, it's rather sad to have the Emacs 22 release drag on and on while we deal with this kind of nitpicky issues.