From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: Pretest? Date: Tue, 13 Mar 2007 10:43:21 +0100 Message-ID: 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=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1173779025 9699 80.91.229.12 (13 Mar 2007 09:43:45 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 13 Mar 2007 09:43:45 +0000 (UTC) Cc: cyd@stupidchicken.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 13 10:43:39 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 1HR3Xe-0003mH-Mt for ged-emacs-devel@m.gmane.org; Tue, 13 Mar 2007 10:43:39 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HR3YP-0005LE-I2 for ged-emacs-devel@m.gmane.org; Tue, 13 Mar 2007 04:44:25 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HR3YC-0005L5-Ia for emacs-devel@gnu.org; Tue, 13 Mar 2007 05:44:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HR3YB-0005Ks-Hj for emacs-devel@gnu.org; Tue, 13 Mar 2007 05:44:11 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HR3YB-0005Kp-Cc for emacs-devel@gnu.org; Tue, 13 Mar 2007 04:44:11 -0500 Original-Received: from ug-out-1314.google.com ([66.249.92.174]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HR3XP-0004yg-Qf for emacs-devel@gnu.org; Tue, 13 Mar 2007 05:43:24 -0400 Original-Received: by ug-out-1314.google.com with SMTP id j3so231843ugf for ; Tue, 13 Mar 2007 02:43:22 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IIbWqBWIprRAyy5PbiWYB+Px+EURv96FUKS8yCr/+KsnBmKW2p8lX6bNkzUDNM5eMRYPyQidmkEYjItQnG53wlXdy08YVDz+xh8saAUuZlGE9mGcNb1+/YZtbnlx/g5w1B/3Phta+cSCvlCZLLS5J0LPJkeWwsEa4KaECV8fHfM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HaucZLV8ec26ADKOrfIChgCw1DCam9INErR5q336EJMc3lKH164Qlf8PWZAbrnoeT5+ubfjsBz/nyN+UnJ96VdJB/xhpcXAzhSHXO/85Jn67fqXhZClrYKr2yYWVZ3IPKtg8rQiq5ICUmZp50lXpw7edDepIRsowxoZqVghngyg= Original-Received: by 10.114.169.2 with SMTP id r2mr2299749wae.1173779001402; Tue, 13 Mar 2007 02:43:21 -0700 (PDT) Original-Received: by 10.114.234.16 with HTTP; Tue, 13 Mar 2007 02:43:21 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-detected-kernel: Linux 2.4-2.6 (Google crawlbot) 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:67851 Archived-At: On 3/13/07, Richard Stallman wrote: > 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. > But server.el should not mess up the command that is being executed. As David pointed out, emacsclient is rarely started in an asynchronous way; usually is as a result of user interaction, either clicking somewhere or typing "emacsclient myfile" in a shell. "Messing up" with the command being executed is exactly what I would expect from such an action. And IIRC, both the current isearch issue and the previous patch to abort recursive editing were prompted by users considering not doing that as a bug. Juanma