Nathan Ridge

cc @fannheyward, maybe you would be interested in this? :smile:

@fannheyward friendly ping :) Today there was a user in the clangd Discord channel who didn't know how to get clangd logs from coc-clangd, and I also didn't know what...

I came across information about how to specify command-line arguments in the coc-clangd repo's README: https://github.com/clangd/coc-clangd?tab=readme-ov-file#configurations

Making note of instructions for getting clangd logs which were posted in the Discord channel: > You can get the path with `:lua print(vim.lsp.get_log_path())` in command mode in any nvim...

And additional details about how specify clangd arguments like `--log=verbose` if not using lspconfig: > In `init.lua`, or wherever they're configuring, and assumes `clangd` is in their path (can probably...

> I think a lot of users use https://github.com/neovim/nvim-lspconfig, though, and there are examples there for configuring servers including passing args to the server when it's started. Documenting the nvim-lspconfig...

I'm going to reopen this because information about how to obtain clangd logs is not included yet in the section about neovim's LSP client, and this is something that users...

@kadircet @hokein I don't have the permission to add you as reviewer in this repo, but could you take a look please?

> Any specific motivation for the patch, apart from increasing docs coverage? I believe this is being used by clangd users at Ericsson, with a modified vscode client. The use...

> If they were to send a didChange, even without forceRebuild set, clangd should still rebuild that preamble nowadays. Oh, interesting! Let me follow up on this; will change the...