Shaun Jackman Sun, 26 Mar 2006 19:28:21 -0800
I've also encountered this same bug with vimpart 4:3.3.2-4 and both vim-gtk 1:6.3-071+1sarge1 and 1:6.4-007+1. Is there any resolution or work-around to this bug?
Thanks, Shaun