On Wednesday, August 15, 2012 8:14:06 PM UTC-5, Christoffer Dall wrote: > On Wed, Aug 15, 2012 at 4:04 PM, Christoffer Dall <[email protected]> > wrote: > > > On Wed, Aug 15, 2012 at 1:53 PM, Ben Fritz <[email protected]> wrote: > > >> On Wednesday, August 15, 2012 12:18:12 PM UTC-5, Christoffer Dall wrote: > > >>> Hi, > > >>> > > >>> I am having a truly annoying issue with gVim on Linux. It happens every > >>> so often that the screen does not redraw itself properly. Instead either > >>> several split panes are black after, for example, running :make or when > >>> switching panes or switching to the gVim window, some lines are are not > >>> updated properly and the code gets all mangled up. > > >>> > > >>> This may be related to this issue: > >>> http://code.google.com/p/macvim/issues/detail?id=409 > > >>> > > >>> I am also running gVim in a relatively high resolution (columns x lines: > >>> 354x90) on Ubuntu Precise. > > >>> > > >>> My version of gVim is 7.3 (patches 1-429). > > >>> > > >>> Any help would be greatly appreciated. > > >>> > > >>> -Christoffer > > >> > > >> Thanks for reporting this. Are you able to find a test procedure which > >> will reliable reproduce it? Are you able to reproduce it at all with most > >> or all of your plugins and customizations removed? Do you, like the person > >> reporting the bug in MacVim, also mostly see the issue when the quickfix > >> error window is open? > > >> > > > > > > Thanks for the fast response. > > > > > > Removing all my plugins avoids the bug. I will go plugin hunting and > > > tell you what I find out. > > > > > > > ok, did some heavy testing today - it turns out it's not a plugin, it > > was merely one line, an important one, in my .gvimrc file: > > > > set gfn=Monospace\ 9 > > > > if this is set, and I use the same window size (in pixels, not vim > > lines) then the redraw issue occurs. > > > > using quickfix seems to "provoke" the issue, but I can't be sure it's > > really the cause. > > > > Any ideas? > > > > thanks! > > > > -Christoffer
I don't have a clue if it would cause the problem, but is "Monospace" actually the name of a single font on your system? If not, maybe try an actual existing font name. -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
