Re: Dialog from emacsclientw.exe must be dismissed (was RE: Best practices for launching Emacs on Windows 7/8)

[Juanma Barranquero <lekktu@gmail.com>]

On Thu, Jun 27, 2013 at 4:28 PM, Ludwig, Mark <ludwig.mark@siemens.com> 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 <RET> 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