Re: Using glib's g_file_monitor_file and g_file_monitor_directory

["Jan Djärv" <jan.h.d@swipnet.se>]

Hello.

5 jun 2013 kl. 15:25 skrev Michael Albinus <michael.albinus@gmx.de>:

> Paul Eggert <eggert@cs.ucla.edu> writes:
> 
>> I tried the new monitor and it made Emacs freeze.
>> I was running "emacs -nw", which I think may help explain the problem.
>> Fedora 17, x86-64.  Here's what I ran:
>> 
>> (gfile-add-watch "/tmp/foo" '() (lambda (ev) (message "%s" ev)))
>> 
>> Here are the diagnostics that were blatted
>> onto my screen before Emacs froze:
>> 
>> (process:11082): GLib-GObject-CRITICAL **: gtype.c:2722: You forgot to
>> call g_type_init()
> 
> I've committed a patch to the trunk which prevents this crash. However,
> if you call "emacs -nw", you won't get any notification. I suppose we
> need an generalized g_main_loop integration, synchronized with the code
> in gtkutil.c.
> 
> Likely, we must move this code out of gtkutil.c and gfilenotify.c. Jan?


Which code?  The glib event loop integration is in xgselect.c.  I think it is called in the -nw case also.  It is only dependent on HAVE_GLIB.
The Gtk+ event loop integration is in xterm.c, it is a separate thing.

	Jan D.