Ok, probably so. If script is able to calculate the end in bytes itself, then the current solution is good. But if it knows how many screen cells it must highlight it is getting almost not feasible to calculate the end col. if case 1 is more common than 2 then current solution is better :)
2014-07-04 14:05 GMT+04:00 Bram Moolenaar <[email protected]>: > > Alexey Radkov wrote: > > > Now it accepts len in screen cells. > > Hmm, that's confusing. Suppose a script isolates a word that it wants > to highlight. Then it's easy to locate the start of the word and the > length with various methods, e.g. using getline(), match() and > matchend(). Then you have the position and size in bytes, not > characters or screen characters. So let's stick to that. > > In the implementation it should be easy to round up, so as to include > the screen cell that contains a highlighted byte. > > > -- > There are 10 kinds of people: Those who understand binary and those who > don't. > > /// 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.
