Go to definition via file link is broken if working directory is not the file directory
See original GitHub issueGiven two Markdown files in the same directory, marksman 1.0.0-dbad138, and helix 22.12 (a4de86e7)
~/Documents/NOTES.md
# Notes
This is a bunch of notes
~/Documents/PEOPLE.md
# People
This is a bunch of people that are referenced in [[Notes]]
If your working directory is ~/Documents, the file link works as expected
If your working directory is ~, the file link does not work as expected
Issue Analytics
- State:
- Created 8 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
VSCode "go to definition" not working
A simple solution that worked for me is that I closed the current workspace and created a new workspace, added the folders which...
Read more >Go to definition not working · Issue #6854
"Go to definition" was working yesterday, but suddenly stop working. I tried to open my project in another computer using Ubuntu 20.04 and...
Read more >Ctrl + Click go to definition not working. : r/vscode
I'm using Python with the Python extension. A bunch of stuff (including go to definition) is missing from the right click menu, intellisense...
Read more >'go to document' broken, with valid relative paths
It is happening to me repeatedly. as shown in the video, if i click on the 'root' file, and navigate from there, it...
Read more >Fix: VS Code Go to Definition Not Working - YouTube
Visual Studio Code (VS Code) is a very popular code editor among the developers of the world. This is due to it's awesome...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@lukepighetti does adding a
.marksman.tomlfile help?Thanks for raising this @lukepighetti! I think what you’re seeing is this https://github.com/artempyanykh/marksman/pull/110
TL;DR: helix used to report bogus workspace folders which caused large file tree scans, which is not cool. The fix makes workspace detection a bit more conservative, but this is better than the previous behavior.
Does your
~/Documentsfolder has a.marksman.tomlor is under version control?