On 4 July 2014, Alexey Radkov <[email protected]> wrote:
> 2014-07-04 18:22 GMT+04:00 Павлов Николай Александрович <[email protected]>:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> >
> > Are you sure you need exactly screen cells? There are the following
> > possible ways to identify position inside a string:
> >
> > 1. Byte offset.
> > 2. Unicode codepoints offset.
> > 3. Composed characters offset (one "composed character" is "one Unicode
> > codepoint with attached composing characters (if any)").
> > 4. Screen cells offset.
> >
>
> Ok, i can imagine all the use cases but i cannot map all of them against
> their usage frequency in majority of the vim plugins. If I have known that
> 4 is very rare i would not have suggested this patch :) ... I just remember
> that LCD asked for 4 in Syntastic plugin.
[...]
Oh, I wasn't *asking* for anything. You claimed in a previous
message that matchaddpos() would be good for syntastic, and I mentioned
some of the reasons why it can't be used. In particular, my point was
that *both* screen characters calculations and byte offset calculation
are useful in practice, not that the former should *replace* the latter.
/lcd
--
--
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.
