You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use bazel for my C++ build and include_prefix, which copies from header files into virtual include folders within the bazel-out directory. When going to definition with LSP to one of these header files, the LSP client does not automatically attach.
Expected behavior
The LSP client should automatically attach to C++ files even in the bazel-out/ subdirectory. I tested clangd does successfully attach to these files.
Steps to reproduce
Open a C++ file within the bazel-out directory, and check :LspInfo() within nvim. It will say 0 clients attached.
System information
ccls version: master
clang version: 11.0.1
Editor: Nvim
Language client (and version): Latest nvim lsp config
The text was updated successfully, but these errors were encountered:
Observed behavior
I use bazel for my C++ build and include_prefix, which copies from header files into virtual include folders within the bazel-out directory. When going to definition with LSP to one of these header files, the LSP client does not automatically attach.
Expected behavior
The LSP client should automatically attach to C++ files even in the bazel-out/ subdirectory. I tested clangd does successfully attach to these files.
Steps to reproduce
Open a C++ file within the bazel-out directory, and check :LspInfo() within nvim. It will say 0 clients attached.
System information
The text was updated successfully, but these errors were encountered: