From: Eli Zaretskii <eliz@gnu.org>
To: Mark Laws <mdl@60hz.org>
Cc: 19688@debbugs.gnu.org
Subject: bug#19688: [patch] add support for emacs daemon on Windows
Date: Sat, 14 Feb 2015 17:24:42 +0200 [thread overview]
Message-ID: <83r3tswm6d.fsf@gnu.org> (raw)
In-Reply-To: <CADemMPP2pZ5Nmuz9cFWJq-fGkh2WBg-PPyBZKo_C3FyS4KN_hA@mail.gmail.com>
> Date: Sat, 14 Feb 2015 22:37:55 +0900
> From: Mark Laws <mdl@60hz.org>
> Cc: 19688@debbugs.gnu.org
>
> On Sat, Feb 14, 2015 at 10:28 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > I don't see why 'WaitForInputIdle' wouldn't work. Can you explain?
> > AFAIU, it waits until the process is idle, which means it did all the
> > initialization and is ready for accepting connections. Am I missing
> > something?
>
> http://blogs.msdn.com/b/oldnewthing/archive/2010/03/26/9985422.aspx
Thanks, it's good to know about those subtleties.
However, after looking at the Emacs initialization code, I think those
problems will not affect Emacs, because we only start the thread that
reads Windows messages inside the call to Frecursive_edit, and by that
time the daemon initialization is already done.
OTOH, there's one other caveat in the documentation of
'WaitForInputIdle': it returns immediately "if the process is a
console application or does not have a message queue". Emacs is built
as a console application, and I'm not sure at which point it begins to
"have a message queue", as far as this function is concerned.
> I can try it if you want, but it seems fragile compared to the event thing.
Please do try it, I think it will either work reliably or not at all.
The reason I'd prefer to use it if it works is because doing so
side-steps the entire issue of how to pass the event ID, which,
together with the code which handles the event, adds non-trivial
amount of code to your patch. It would be nice to avoid that, if
possible.
Thanks.
next prev parent reply other threads:[~2015-02-14 15:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 19:18 bug#19688: [patch] add support for emacs daemon on Windows Mark Laws
2015-01-25 20:34 ` Eli Zaretskii
[not found] ` <CADemMPM+Tix-6FJ+CO3HA8y7Cq6AV0kv_e6_qn7BaSw1QMOwTQ@mail.gmail.com>
2015-01-26 6:00 ` Eli Zaretskii
2015-01-26 7:40 ` Mark Laws
2015-01-26 11:56 ` Daniel Colascione
2015-01-27 8:40 ` Mark Laws
2015-01-30 0:36 ` Mark Laws
2015-01-30 6:28 ` Eli Zaretskii
2015-02-13 0:07 ` Mark Laws
2015-02-13 8:49 ` Eli Zaretskii
2015-02-14 12:10 ` Eli Zaretskii
2015-02-14 13:16 ` Mark Laws
2015-02-14 13:28 ` Eli Zaretskii
2015-02-14 13:37 ` Mark Laws
2015-02-14 15:24 ` Eli Zaretskii [this message]
2015-02-14 16:34 ` Mark Laws
2015-02-14 16:53 ` Eli Zaretskii
2015-02-14 16:57 ` Mark Laws
2015-02-14 17:23 ` Eli Zaretskii
2015-02-14 17:30 ` Mark Laws
2015-02-14 17:42 ` Eli Zaretskii
2015-02-14 17:57 ` Mark Laws
2015-02-14 18:26 ` Eli Zaretskii
2015-02-14 19:21 ` Mark Laws
2015-02-14 19:29 ` Eli Zaretskii
2015-02-14 21:15 ` Mark Laws
2015-02-19 16:31 ` Mark Laws
2015-02-19 16:56 ` Eli Zaretskii
2015-02-21 13:03 ` Eli Zaretskii
2015-02-21 19:30 ` Mark Laws
2015-02-27 14:26 ` Eli Zaretskii
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=83r3tswm6d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19688@debbugs.gnu.org \
--cc=mdl@60hz.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).