-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C/C++ intellisense not working with ssh-fs folders added to workspace #27
Comments
It's similar to the issue you've already seen, namely microsoft/vscode#51700. The extension providing the intellisense, syntax coloring, ... has to add support for FileSystemProvider-based files. Right now, VSCode hasn't released an API (similar to microsoft/vscode#48034) to even allow extensions to access such files, but it seems they'll be adding one soon. I'll close this issue for now, as it isn't something I (or maintainers of other extensions) can fix right now. |
Any updates on this feature? |
Doesn't seem like it: microsoft/vscode-cpptools#2268 Mind that I can't do anything about other extensions (like those providing C++ intellisense) not being able to use remote filesystems. The only solution, besides waiting for them to add support, is to use VS Code's Remote SSH instead, where VS Code (and all extensions) run on the server itself. |
Yeah. I started using remote SSH. It does not work as good SSHFS unfortunately and consumes a lot of memory. |
Hello,
The ssh-fs works well for mounting remote directories, navigating directory structures (including symlinks, thanks for that!), and editing files. However, intellisense fails to parse the files in these "mounted" directories. I originally filed a bug with vscode, however, they say the issue is with the extension. See microsoft/vscode#54189
Is there something wrong with the way I'm specifying the folder in c_cpp_properties.json (see below)?
Thank you for your assistance with this.
Cheers!
Steps to Reproduce:
My sshfs config:
My code-workspace
How I add it to c_cpp_properties.json
The text was updated successfully, but these errors were encountered: