https://icyveins7.github.io/tags/neovim/Recent content in Neovim on icyveins7's blogHugoen-usThis work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.Tue, 26 Mar 2024 20:00:00 +0800https://icyveins7.github.io/posts/2024/03/getting-rid-of-clangds-errors-on-windows/Tue, 26 Mar 2024 20:00:00 +0800https://icyveins7.github.io/posts/2024/03/getting-rid-of-clangds-errors-on-windows/<blockquote> <p>My first steps into migrating to neovim, some clangd problems and my solutions..</p> </blockquote> <h1 id="kickstartnvim-brought-me-here">Kickstart.nvim brought me here</h1> <p>I started using vim motions in VSCode a month or two ago, and decided to actually try to see if neovim would work for me. Honestly, I probably wouldn&rsquo;t have gone down this path if <a href="https://github.com/nvim-lua/kickstart.nvim">kickstart.nvim</a> didn&rsquo;t exist. But it does, and I tried it, and it looks like I&rsquo;m here to stay.</p> <h1 id="clangd-as-my-first-lsp">clangd as my first LSP</h1> <p>In kickstart.nvim&rsquo;s template, <code>clangd</code> is listed as an example LSP, so I decided to uncomment that line and try it out. I opened my <a href="https://github.com/icyveins7/ffs">ffs</a> repository at the time, and was immediately greeted with a flood of warnings on my code. This brings us to the first problem.</p>