chromatica.nvim

chromatica.nvim copied to clipboard

Chromatica is vulnerable to a race condition where it tries to access buffers that other plugins have deleted. Details (and recommendations on how to fix it) are here: https://github.com/neovim/neovim/issues/9399#issuecomment-450210368

duganchen

If I set my filetype to "c.doxygen" to get doxygen doc comment syntax support, most of the colors of Chromatica doesn't work. Variables and function declarations cease being highlighted however...

ghost

Please add support for reading flags from .ycm_extra_conf.py from YouCompleteMe plugin.

cryptomilk

[RFC] Possible performance improvements using neovim Live Updates

2

Hello! A friend showed me your Chromatica plugin which looks like it has a lot of potential. Personally I'm very excited to see some new async Syntax engines since vim's...

phodge

Highlighting is not updated on viewport change

3

Hey, chromatica does not update highlighting when only the viewport is changed (e.g. by pressing `zz` or ``) and the cursor stays in place. Would it maybe be better to...

IngoMeyer441

Reread compilation flags after changing the working directory

1

Is it possible to reread compilation flags after changing the working directory in vim? With this feature it would be possible to use multiple `.clang` files in one nvim process.

IngoMeyer441

Chromatica works poorly with Solarized Color Scheme

5

Hi! I've tried to setup Chromatica with my vim-colors-solarized colorscheme setup and noticed major issues: * Default colors are overriden * Similar syntax constructions are colored differently (see includes for...

kirillbobyrev

user defined Type not colored as Type

3

At open file:   At rewrite `House`: 

davidkennedydev

size_t colored as the next token

2

Without explicit `using std::size_t`:    Explicit define `using std::size_t` fix colors.

davidkennedydev

Reserved keywords not colored

4

 Why the `while` and `if` keywords are not colored?

davidkennedydev