Christian wrote:
> On Sa, 23 Jun 2018, Israel Chauca Fuentes wrote: > > > Set up: Run vim with this command in a 90 columns wide terminal window: > > > > vim -Nu NONE -i NONE -c 'set linebreak vartabstop=10,20,30,40,50,60,70' > > -c 'call setline(1, "\tx\tx\tx\tx")' > > > > Expected: After this, the fourth 'x' should be on the second line with the > > cursor. > > > > Result: The fourth 'x' is displayed in the first line, very close to the > > third 'x'. > > > > This is the output of `vim --version`: > > Thanks for the clear explanation. The attached patch fixes it (only > visible in the mailinglist). I took the liberty to turn your example > into a test. Thanks. Can we make the test work with a narrower window? Mostly 80 chars is used, I don't think the CI runs with a larger terminal, resulting in the test being skipped. -- hundred-and-one symptoms of being an internet addict: 105. When someone asks you for your address, you tell them your URL. /// 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.
