Georgiy Komarov

This plugin works with any LSP server that supports `textDocument/codeLens`. Please check the documentation of `rust-analyzer` to make sure that it supports `textDocument/codeLens` request, and you have configured it correctly.

Thanks for the report! I suppose, the problem is in the compiled binary for Windows. I build it manually on my second machine. So we have to rebuild the binary...

It can be quick fixed with something like this: https://github.com/jubnzv/gruvbox/commit/830245080733123861c936bfb8a58e1da7d4a09e Result:  But I have no idea how to implement [all other](https://github.com/neovim/neovim/blob/f5406dfe7772dca82e31f27c042c5718198f0ec8/runtime/syntax/doxygen.vim#L504) doxygen.vim options without long copy-pasting into gruvbox code.

No. But this is possible using my tool: https://github.com/jubnzv/iec-checker. Install it according to README and use something like this: ```bash iec_checker path/to/file.st -dump true ``` This will generate an AST...

> Does it support the IL standard language? No, it doesn't support IL. But it will work well with ST used in matiec. I'm not actively working on this utility...

> implemented a pretty-printer, but we still don't have a formatter What do we need to prepare a production version of the formatter? From my perspective, it would be nice...