On 3/29/11 10:55 AM, Daniel Colascione wrote:
> On 3/28/11 3:20 PM, chad wrote:
>> If the method works out in practice, how would people feel about a
>> patch to emacsclient adding a flag to send such signals?
> 
> That would be fine. For NT Emacs, the best approach would be for
> emacsclient to suspend all threads in the target Emacs process, then use
> CreateRemoteThread to inject code into a running Emacs.  This code would
> trip the debugger the same way the signal handler in my patch does, then
> resume the rest of Emacs.

Err, after actually *reading* w32term.c and w32fns.c, it looks like a
normal window message would suffice.  No need for code injection.