From: "Ludwig, Mark" <ludwig.mark@siemens.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
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 14:28:12 +0000 [thread overview]
Message-ID: <BC5672F8AD4C054BAF167C9801500D1ABCB5899D@USSLMMBX003.net.plm.eds.com> (raw)
In-Reply-To: <CAAeL0SQQC_oFZ=HS7X-M_PHXXHnYwjCFnpdM+u+y3oyFiCpsMw@mail.gmail.com>
> From: Juanma Barranquero, Thursday, June 27, 2013 9:02 AM
>
> On Thu, Jun 27, 2013 at 3:29 PM, Ludwig, Mark <ludwig.mark@siemens.com>
> wrote:
>
> > That said, the pop-up error really shouldn't need dismissal by the
> > user when there is either ALTERNATE_EDITOR or --alternate-editor. In
> > that configuration, it's not clear that the error should even be
> > reported -- except perhaps as a warning (to inform the user why the
> > alternate editor was launched).
>
> The error says that emacsclientw found a server file for a process it
> could not connect. That is useful.
I don't agree. Why is it useful to make the user click OK (the only
available button) /before/ launching the alternate editor?
> For example, emacs could still be
> running, just not attending to server connections for some reason.
> It's better to give the user the information *and* let him decide (by
> clicking on OK, or doing something else) how to fix things.
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.
What else do you think I can do before clicking OK? As far as
investigating what's wrong with a running Emacs, it doesn't matter
whether I look before or after clicking OK, because emacsclientw has
done whatever it's going to do to the running Emacs, and the alternate
editor (in my case) will be a separate instance of Emacs.
Thanks,
Mark
next prev parent reply other threads:[~2013-06-27 14:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 18:17 Dialog from emacsclientw.exe must be dismissed (was RE: Best practices for launching Emacs on Windows 7/8) Ludwig, Mark
2013-06-26 18:47 ` Richard Copley
2013-06-26 23:11 ` Juanma Barranquero
2013-06-27 0:04 ` Ludwig, Mark
2013-06-27 0:34 ` Juanma Barranquero
2013-06-27 13:29 ` Ludwig, Mark
2013-06-27 14:01 ` Juanma Barranquero
2013-06-27 14:28 ` Ludwig, Mark [this message]
2013-06-27 14:51 ` Juanma Barranquero
2013-06-27 15:34 ` Ludwig, Mark
2013-06-27 20:50 ` Juanma Barranquero
2013-06-27 21:27 ` Ludwig, Mark
2013-06-27 22:14 ` Juanma Barranquero
2013-06-27 21:35 ` Ludwig, Mark
2013-06-27 22:17 ` Juanma Barranquero
[not found] ` <mailman.2633.1372368937.22516.help-gnu-emacs@gnu.org>
2013-06-28 7:38 ` Jason Rumney
2013-06-28 17:55 ` Richard Copley
2013-06-28 18:31 ` Richard Copley
2013-06-29 3:52 ` Ludwig, Mark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BC5672F8AD4C054BAF167C9801500D1ABCB5899D@USSLMMBX003.net.plm.eds.com \
--to=ludwig.mark@siemens.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).