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'm trying to use clangd installed in a podman container. I've configured it so that running the language server is done by the "podman run" commandline:
But the (obvious) problem is that file paths for the system headers is different inside the container and in Vim.
I can mount any container's directory to anywhere on my host, with an exception that most of the time it will not be the same path, so I'm wondering: does vim-lsp support filename remapping from/to what the LSP generates/expects?
For example, some function that would convert a path sent to the LSP, and another function that would convert a path got from LSP? That would probably be enough for me (I think) to use an LSP installed inside podman container.
The text was updated successfully, but these errors were encountered:
Translates between client paths (as seen by a remote editor) and server paths (where clangd sees files on disk). Comma separated list of '<client_path>=<server_path>' pairs, the first entry matching a given path is used. e.g. /home/project/incl=/opt/include,/home/project=/workarea/project
I'm trying to use
clangd
installed in apodman
container. I've configured it so that running the language server is done by the "podman run" commandline:But the (obvious) problem is that file paths for the system headers is different inside the container and in Vim.
I can mount any container's directory to anywhere on my host, with an exception that most of the time it will not be the same path, so I'm wondering: does vim-lsp support filename remapping from/to what the LSP generates/expects?
For example, some function that would convert a path sent to the LSP, and another function that would convert a path got from LSP? That would probably be enough for me (I think) to use an LSP installed inside podman container.
The text was updated successfully, but these errors were encountered: