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 13:29:48 +0000 [thread overview]
Message-ID: <BC5672F8AD4C054BAF167C9801500D1ABCB5887A@USSLMMBX003.net.plm.eds.com> (raw)
In-Reply-To: <CAAeL0STT01PODpu4Js-pUjQ4GgGWevYWp+Se-r7Ka1vc6Nz2sg@mail.gmail.com>
> From: Juanma Barranquero, Wednesday, June 26, 2013 7:35 PM
>
> On Thu, Jun 27, 2013 at 2:04 AM, Ludwig, Mark <ludwig.mark@siemens.com>
> wrote:
>
> > Secondly, it does not involve emacs(!). The problem is purely in
> [...]
> > "Connection refused": "No connection could be made because the target
> > machine actively refused it."
>
> Hm. I'm going to borrow the cristal ball from a friend and ask: Do you
> exit Emacs before turning off your computer?
Usually, yes (because if I haven't saved in every buffer, I don't like
leaving auto-save files around).
> As you start Windows and before trying emacsclientw.exe, if you look
> at %HOME%\.emacs.d\server (whenever your %HOME% happens to be), do you
> find there a file named server?
Not usually, no, but if I deliberately leave Emacs running when
telling Windows to restart, then I do find a "server" file in that
directory (and the pop-up error appears).
> If so, does the problem disappear if you delete that file before
> running emacsclientw.exe for the first time?
Yes.
I was not aware that I was not exiting Emacs, but in a hard Windows
abort/restart, of course, there is no opportunity to exit Emacs.
Still, I appreciate that the problem is arguably external to Emacs.
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).
Thanks!
Mark
next prev parent reply other threads:[~2013-06-27 13:29 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 [this message]
2013-06-27 14:01 ` Juanma Barranquero
2013-06-27 14:28 ` Ludwig, Mark
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=BC5672F8AD4C054BAF167C9801500D1ABCB5887A@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).