Re: [PATCH] system-type cygwin with window-system w32

[grischka]

Daniel Colascione wrote:
> If it works, /dev/windows would allow us to get rid of not only the self-pipe
> and the clipboard thread, but the UI thread as well, though it'd be easier to
> keep the last of these for compatibility for the NT build.  Thanks.

Actually the NT build works quite well with one single thread.
Already tested here.

> By the way: why do we use a separate UI thread in the NT case at all?  AIUI, we
> can do everything we need asynchronously via overlapped IO, so we should never
> have to block and not pump messages.

The 'sys_select' wrapper DOES pump messages, just for the wrong
thread.  So it needs the thread because it has the thread. :)

Well, there are two other things needed:
* peek for messages in the QUIT macro (say via ELSE_PENDING_SIGNALS)
  which is for C-g to interrupt lisp.
* break command_loop_1() such that it can be used to handle just one
  event which is to handle scrollbar messages because the widgets
  run their own message loop deep in windows.  Otherwise all the
  scrolling would happen only after you release the mouse button.

--- grischka