Thanks for your answer. :o) 2009/5/25 Andreas Bernauer <[email protected]>
> I can't see this behavior in GVim (Gnome), v 7.1.138 > Maybe switching to a newer gvim version will remedy the problem? > I'm using GVim v. 7.1.314, so that shouldn't be the problem. Actually, it seems like I wasn't completely right before. This "bug" doesn't occur when the GVim window is just maximized, but only when the window is maximized and split using :vsplit. This doesn't seem to be a problem when using Vim from a terminal. > Alternatively, maybe using 'set fo-=t' instead of 'set fo=l' is enough. Unfortunately this didn't do the trick. Thanks for your help anyway! :o) -- Kristoffer --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
