Christian Brabandt wrote: > > > Bram, > > > I have lately worked with very narrow windows¹, and I noticed some > > > problems (and even crashes). > > > > > > 1) Setting the foldcolumn might actually fill the complete window. E.g. > > > can set fdc=12 and make the current window exactly 12 chars wide. So > > > one has a window, that does not draw any text. Patch > > > check_fdc_width.diff fixes that > > > 2) for very narrow window, nv_screengo might actually crash with a > > > floating point exception. This is caused be width1 or width2 being > > > zero. Additionally, it might happen, that a tab might span several > > > screen lines and then using gk and gj do not work as expected. Patch > > > screengo.diff fixes those two errors. > > > > This patch causes test 39 to fail. > > At least include the part, that checks for width1 and width2 being > unequal to zero.
Looks like only width2 can cause a problem. > Perhaps the other part is more or less a theoretical problem (and that > caused the problem). I'll leave that to you, hopefully you remember the problem you were fixing. -- In a world without fences, who needs Gates and Windows? /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
