On Sun, Dec 18, 2016 at 10:09 PM, Davit Samvelyan <[email protected]> wrote: > Justin, > > We had a small discussion with neovim team here > https://github.com/Valloric/ycmd/pull/291 > when the server side of token extraction were being forged. > At that time someone was working on buffer specific matches based on signs > implementation, but I lost track at some point. How it was/is going? Did you > mention the same thing? > Author was claiming that matches for the whole buffer can be added without > slowdown.
That's the nvim_buf_add_highlight() API function[1] I mentioned. It is used at least by the chromatica.nvim plugin[2]. Also note the nvim_call_atomic() function[3] supports batching API calls in a single RPC request. This discussion is worth a look: https://github.com/arakashic/chromatica.nvim/issues/18 > Another must have for semantic highlighting is knowledge of the dirty regions > where tokens need to be updated This PR may help with that, and the author wrote a proof of concept application: https://github.com/neovim/neovim/pull/5269 [1] https://github.com/Valloric/ycmd/pull/291#issuecomment-171752613 [2] https://github.com/arakashic/chromatica.nvim [3] https://github.com/neovim/neovim/pull/4568 --- Justin M. Keyes -- -- 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.
