From: Philip M. <phi...@go...> - 2009-11-21 20:36:08
|
hi, This bug has been annoying enough to stop me from using vimplugin for quite a while. I thought I'd look into doing a fix myself. Can anyone give me some background - has anyone tried to fix this before? It's a bit of a sticky problem I think. Win32 is not flexible for this kind of thing. The root of the problem seems to be that the vim editor window belongs to the gvim process rather than to eclipse. 2 approaches suggest themselves: 1) make eclipse the parent window instead of gvim 2) make gvim output into the eclipse SWT window that would ordinarily be used for the text editor buffer solution 1 isn't likely to work (win32 will probably refuse). solution 2 would be a better bet, but would mean frigging around with gvim, possibly a hell of a lot. Any comments? Thanks Philip |