This bug was reported regarding MacVim, but seem to be of broader relevance. Just read 'MacVim' as 'gvim' and find yourself a suitably long path, or make yourself a suitable narrow GUI window and it should work (well, not work!). Here is the discussion:
Nico Weber wrote: > On 07.06.2008, at 19:09, Ben Schmidt wrote: >>>>>>> 1. enter `:e` and the name of file with a very long path. For >>>>>>> example, enter `:e $VIMRUNTIME/tut<tab>/tutor.ko.utf-8`. This >>>>>>> will expand to `:e /Applications/_Nico/MacVim.app/Contents/ >>>>>>> Resources/vim/runtime/tutor/tutor.ko.utf-8`, which is too long >>>>>>> to fit in one line if you have 80 columns. 2. Hit ⌘⇥, then hit >>>>>>> ⌘⇥ again to deactivate and reactivate MacVim. >>>>>>> >>>>>>> Result: The ex line is drawn several times. This actually looks >>>>>>> more like a core vim bug, but I don't see it on Ubuntu (might be >>>>>>> because I'm using only vim7.1 on Ubuntu, not the latest svn >>>>>>> version. Is someone on this list using the latest svn version of >>>>>>> gvim on Linux or win32 and can try to reproduce the bug?). >>>>>>> >>>> I get several lines on top of each other. It seems that only happens >>>> if you have these lines in your _vimrc: >>>> >>>> au WinEnter * set cursorline >>>> au WinLeave * set nocursorline >>>> au FocusGained * set cursorline >>>> au FocusLost * set nocursorline >>>> >>>> I still don't see it in Ubuntu, even if I add these lines over there >>>> (again, possibly because I don't use the latest svn version of vim >>>> over there). This might be related to >>>> http://groups.google.com/group/vim_dev/browse_thread/thread/41883073aa7a62f3/2d99550bf818febf?lnk=st&q=vim+focusgained#2d99550bf818febf >>>> ? >>>> >>> I see it in GTK2 GVIM and pre-new-menu MacVim. I'll see if I can >>> track down where it came from, since we know it's a recent addition. >>> >> For me svn revision 286, which I believe corresponds to Vim 7.1 >> without patches, still exhibits the problem in GTK2. Which version is >> it where you don't see it, Nico? > > I don't see it in vim7.1, patches 1-138. I still see it in that version. I guess something else must be different on your Ubuntu system rather than this being a regression. Looks like a current bug. CCing vim_dev. Are others able to reproduce/fix this? Perhaps one for the to do list, Bram? Ben. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
