Marius Gedminas wrote:
> Guido, thank you for that reference!
>
> Do you have a link to the other side of the discussion (i.e. with Bram
> and other Vim developers, assuming there are other Vim developers)?
>>From the thread referenced in the bugzilla entry it does seem as if it's
> Vim that's using a library incorrectly.
Sorry, that was private correspondence with Bram. Basically vim has its
own main loop and enters and leaves the GTK main loop at pretty much any
event. Bram is fine with this but the GTK devs disapprove this usage.
Point is, that GTK changed its behavior in an undocumented way and that
the GTK folks acknowledge this as a problem. So it's either the GTK devs
revert the behavior of RecentManager or somebody makes substantial
changes to vim.
If you want even more details on the vim side you can take a look at the
GTK specific code here:
Marius Gedminas wrote:
> Guido, thank you for that reference!
>
> Do you have a link to the other side of the discussion (i.e. with Bram
> and other Vim developers, assuming there are other Vim developers)?
>>From the thread referenced in the bugzilla entry it does seem as if it's
> Vim that's using a library incorrectly.
Sorry, that was private correspondence with Bram. Basically vim has its
own main loop and enters and leaves the GTK main loop at pretty much any
event. Bram is fine with this but the GTK devs disapprove this usage.
Point is, that GTK changed its behavior in an undocumented way and that
the GTK folks acknowledge this as a problem. So it's either the GTK devs
revert the behavior of RecentManager or somebody makes substantial
changes to vim.
If you want even more details on the vim side you can take a look at the
GTK specific code here:
http:// vim.svn. sourceforge. net/viewvc/ vim/vim7/ src/gui_ gtk_x11. c?view= markup vim.svn. sourceforge. net/viewvc/ vim/vim7/ src/gui_ gtk.c?view= markup
http://
If you want to discuss this further I think it would be more appropriate
if you mail me privately or take this to <email address hidden> .