On Sun, Mar 8, 2015 at 4:59 AM, Christian Brabandt <[email protected]> wrote: > This only happens in vi mode (or more specifically, when cpo contains > the 'n' flag). Looks like Vim gets confused, because the first visible > screen line already shows the sbr string and that is not expected for a > screen row, that contains a line number.
Thanks for the explanation. So this bug is not really about rnu + show break. nu + nornu + showbreak + cpo+=n will also trigger it. nazri -- -- 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.
