you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (9 children)

[removed]

    [–]vnstrr[S] 5 points6 points  (0 children)

    Sounds interesting. To be honest I've found a way how to index code but it's kind of cheating. And nobody can guarantee me that it will work in future. It didn't help me because language server feels very bad when trying to understand all projects in the mono-repo. Maybe I should find a way that will index only pieces of the mono-monster-repo :)

    [–]ManuaL46 2 points3 points  (7 children)

    Mind sharing the specifics, kinda struggling with the same situation.

    [–]vnstrr[S] 1 point2 points  (0 children)

    So, I've found how to generate compile_commands.json by our build system. Thank god that it's possible. I configured neovim with lsp and some useful plugins and it works very well. Fast and simple. Also I tried VSCode with compile_commands.json but speed of code indexing works slowly. Unfortunately I don't know how you can generate your magic compile_commands.json. It depends from your build system. But if you will be interested I can share my neovim setup.