From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.help Subject: Re: Dialog from emacsclientw.exe must be dismissed (was RE: Best practices for launching Emacs on Windows 7/8) Date: Thu, 27 Jun 2013 16:51:55 +0200 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1372344769 10677 80.91.229.3 (27 Jun 2013 14:52:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 27 Jun 2013 14:52:49 +0000 (UTC) Cc: "help-gnu-emacs@gnu.org" To: "Ludwig, Mark" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jun 27 16:52:51 2013 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UsDZ5-000714-3T for geh-help-gnu-emacs@m.gmane.org; Thu, 27 Jun 2013 16:52:51 +0200 Original-Received: from localhost ([::1]:59707 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsDZ4-0003BD-Nn for geh-help-gnu-emacs@m.gmane.org; Thu, 27 Jun 2013 10:52:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56112) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsDYs-00039i-A8 for help-gnu-emacs@gnu.org; Thu, 27 Jun 2013 10:52:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UsDYq-0006iC-Vg for help-gnu-emacs@gnu.org; Thu, 27 Jun 2013 10:52:38 -0400 Original-Received: from mail-ea0-x22b.google.com ([2a00:1450:4013:c01::22b]:48322) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsDYq-0006i6-Oh for help-gnu-emacs@gnu.org; Thu, 27 Jun 2013 10:52:36 -0400 Original-Received: by mail-ea0-f171.google.com with SMTP id m14so465441eaj.30 for ; Thu, 27 Jun 2013 07:52:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=4TK/U0bk+v5eosjbZr6Ax2VWMq9P6fE4F4psNfSI4RI=; b=g4BW4OdOARmDQPDaunJh6bWSCSCNrj9Q9N2ZYItZot0eJTcbX7flttGh3VY8x0I1bx sMg7ivtYTgikk4HB0f+JKaPKyCMql7fN4dHGm5FNb07Fgzvx3psokUnn3UaovtsWJZZf h+zvXPFH+0QVoVdeBVvcvsScMaK2QV7PHbOfGIMer9zEIREfpy9P5kcD2aN7yVugZXjX M7Ww17wXGltjY7wBR/G1h0aMUkqYoDVw+vRHxN3fE7r0jwBxoObykp5zYDWhq0K9PGke UH1pZKDMjgmK6dfzud/KvJxBjReifYdVv5feyUwsMxiuQSF5NAIoUxDS7NTv0CO5pymf Vmnw== X-Received: by 10.15.76.71 with SMTP id m47mr9298743eey.70.1372344755974; Thu, 27 Jun 2013 07:52:35 -0700 (PDT) Original-Received: by 10.14.142.4 with HTTP; Thu, 27 Jun 2013 07:51:55 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c01::22b X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:91779 Archived-At: On Thu, Jun 27, 2013 at 4:28 PM, Ludwig, Mark wrote: > I don't agree. Why is it useful to make the user click OK (the only > available button) /before/ launching the alternate editor? Because if we don't say anything, the user won't be aware that there's a problem. In fact, if we didn't say anything, we would not be having this conversation in the first place. That message tells the user that Emacs exited unexpectedly. I agree that it is not useful for *your* use case, but that does not mean that it is not generally useful. I, for once, much prefer getting these error messages than not getting them (so I can try and find what's going wrong behind my back). > Let's say you're correct that there is a running Emacs that's not > responding, so the dialog information is reporting an "interesting" > situation. I claim that it /still/ doesn't matter, because > emacsclientw has made its only attempt to connect to the > supposedly-running server (which failed) and all the user can do is > click OK, after which emacsclientw will launch the alternate editor > (if any). If there were a "Retry" button, that would be /very/different. I didn't say that Emacs is not responding, I said that Emacs is not responding to server requests. Perhaps you inadvertedly deactivated the server mode, and jus M-x server-mode will activate it again without having to exit and reload Emacs. If that seems far-fetched to you, well, it's happened to me more times that I could count. J