We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thank you for the implementation of this amazing idea!
On Windows I noticed that the "Go to code" feature in the feature hover does not work.
The error message from VSCode is "Unable to resolve resource ...".
It does however work, when I prepend the registry path with file:/// or file:// when the registry path already starts with a slash.
file:///
file://
The same problem and solution applies for using VSCode from a Windows machine on a Linux based remote.
The text was updated successfully, but these errors were encountered:
Hello @b2m, thanks for the catch! We'll take a look at this.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Thank you for the implementation of this amazing idea!
On Windows I noticed that the "Go to code" feature in the feature hover does not work.
The error message from VSCode is "Unable to resolve resource ...".
It does however work, when I prepend the registry path with
file:///
orfile://
when the registry path already starts with a slash.The same problem and solution applies for using VSCode from a Windows machine on a Linux based remote.
The text was updated successfully, but these errors were encountered: