Christian Wellenbrock wrote: > On Monday, June 3, 2013 9:29:03 AM UTC+2, mattn wrote: > > On Monday, June 3, 2013 7:33:39 AM UTC+9, Christian Wellenbrock wrote: > > > > > I recently noticed the following inconsistency regarding the > > > 'fillchars' and 'statusline options:
[...] > > I don't make sure this patch. This patch seems not modified > > screen.c, Is this support double width characters? > > > > Thanks. > > Yes, this patch does not modify screen.c, because screen.c is already > capable of handling multi-byte characters, as you can see in the first > of my three examples. > > I have not tried using it with double width characters. The original > intent was to support single width multi-byte characters. I don't know > if double width character support is as easy to implement. I would think double-width fill characters are not useful. We could just mention in the docs that they won't work. Better is to reject them and fall back to "-" as before. -- Time is money. Especially if you make clocks. /// 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/groups/opt_out.
