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
Navigation to definition or references fails on Windows #27
Comments
A fix may need some time, as we all have Linux machines here. |
@danwos, as you can see, I have a lead on fixing this proble: using the After this change, the explorer view is also broken for me, but that may well be because I'm doing something wrong in terms of setup for VSCode extension development, since it's not something I've done before. I'm not likely to do any more work on this now because I'm looking into using Logseq for Planguage requirements instead. Thanks for your quick response at the time, though! |
@danwos We have also run into this issue. All my colleges are exclusive on Windows. I haven't got any vscode-extension or typescript skills, so I may not be able to fix this my self. But if I can help test any fixes then let me know. |
I'm using extension version 0.2.1, VSCode version 1.78.2, on Windows 10.
I'm not able to jump to definitions or references from a need ID in an option like
links
. Due to #26 my configured workspace paths are using relative paths likesource
andbuild/needs/needs.json
, without${workspaceFolder}
. It may be that this issue would be fixed if #26 were fixed.If I add
${workspaceFolder}
, I get errors like the following in the extension's output, and there's nothing from the extension UI for hover or navigation.If I leave out
${workspaceFolder}
then, for a file in<my_workspace>/source/foo.rst
, VSCode tries to open\source\foo.rst
. As you may know, on Windows this meansX:\source\foo.rst
whereX
is the current drive of the VSCode process.The text was updated successfully, but these errors were encountered: