To Correctly Handle links for shortened-paths introduced in the updated stacktrace of Julia 1.6.0 #777
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fix will correctly handle links to shortened-paths introduced in the new stacktrace of Julia 1.6.0 by expanding the tilde "~" symbol to be the home directory in the link only (will not change the actual path on screen in the stacktrace). This is tested on a Windows 10 machine, but it should work for MacOs and Linux as well (confirmation would be appreciated).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fix will correctly handle links for shortened-paths introduced in the updated stacktrace of Julia 1.6.0, so clicking on a shortened-path in the new stacktrace should take you to the correct code position.
This is done by expanding the tilde "~" symbol to be the home directory in the link only (will not change the actual path on screen in the stacktrace).
This is tested on a Windows 10 machine, but it should work for MacOs and Linux as well (confirmation would be appreciated).