From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Pretest? Date: Tue, 13 Mar 2007 11:09:07 +0100 Message-ID: <86r6rtzc8s.fsf@lola.quinscape.zz> 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 1173780577 15114 80.91.229.12 (13 Mar 2007 10:09:37 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 13 Mar 2007 10:09:37 +0000 (UTC) Cc: Juanma Barranquero , cyd@stupidchicken.com, rms@gnu.org, emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 13 11:09:30 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 1HR3wZ-00081e-BS for ged-emacs-devel@m.gmane.org; Tue, 13 Mar 2007 11:09:23 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HR3xK-0008So-Dj for ged-emacs-devel@m.gmane.org; Tue, 13 Mar 2007 05:10:10 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HR3x9-0008SV-QR for emacs-devel@gnu.org; Tue, 13 Mar 2007 06:09:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HR3x9-0008SJ-Ad for emacs-devel@gnu.org; Tue, 13 Mar 2007 06:09:59 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HR3x9-0008SG-31 for emacs-devel@gnu.org; Tue, 13 Mar 2007 05:09:59 -0500 Original-Received: from pc3.berlin.powerweb.de ([62.67.228.11]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HR3wN-0008Kl-D2 for emacs-devel@gnu.org; Tue, 13 Mar 2007 06:09:11 -0400 Original-Received: from quinscape.de (pd95b0fdb.dip0.t-ipconnect.de [217.91.15.219]) by pc3.berlin.powerweb.de (8.9.3p3/8.9.3) with ESMTP id LAA09735 for ; Tue, 13 Mar 2007 11:09:07 +0100 X-Delivered-To: Original-Received: (qmail 15580 invoked from network); 13 Mar 2007 10:09:08 -0000 Original-Received: from unknown (HELO lola.quinscape.zz) ([10.0.3.43]) (envelope-sender ) by ns.quinscape.de (qmail-ldap-1.03) with SMTP for ; 13 Mar 2007 10:09:08 -0000 Original-Received: by lola.quinscape.zz (Postfix, from userid 1001) id 6C32BC1600; Tue, 13 Mar 2007 11:09:07 +0100 (CET) In-Reply-To: (Andreas Schwab's message of "Tue\, 13 Mar 2007 10\:52\:51 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-detected-kernel: Linux 2.4-2.6 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:67854 Archived-At: Andreas Schwab writes: > "Juanma Barranquero" writes: > >> On 3/13/07, Richard Stallman wrote: >> >>> 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. > > I agree. I have sometimes wondered why my emacsclient frame does not pop > up (I have set server-window to create a new frame) when I have forgotten > to exit an isearch in another frame. Normally almost any command will > abort the isearch. > >> 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. > > Which I agree with aborting isearch, I don't agree with aborting a > recursive editing, since the latter is not as much a modal thing. To make that clear: my suggestion was about exiting the minibuffer. However, if point moves to the buffer window, exiting the minibuffer can probably be left to the normal recursive-minibuffer mechanisms that kick in when the user tries using the minibuffer other than moving back into it with C-x o. So that suggestion of mine was probably not really an improvement. -- David Kastrup