Re: Using glib's g_file_monitor_file and g_file_monitor_directory

[Stefan Monnier]

>> AFAIK this event is only inserted when we're waiting for user input
>> (see record_asynch_buffer_change).  Furthermore, I'd argue that the
>> right way to handle such switches is to consider them as bugs (i.e. we
>> could just throw BUFFER_SWITCH_EVENT away).
> According to the comments, record_asynch_buffer_change is also used for
> forcing a redisplay in xterm.c and w32term.c. This must be implemented
> otherwise, if we throw BUFFER_SWITCH_EVENT away.

Indeed.  But the fact that remains that it being linked to the "key
event queue" is not a problem, so it doesn't need to (and shouldn't) be
moved to some other event queue, contrary to dbus, etc...


        Stefan