You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I try opening a file with the @ symbol in its path from the scan results, it fails, because @ gets encoded as %40, and I get the "Unable to resolve nonexistent file" error -- see the screenshot.
To Reproduce
Just have file paths containing the @ in them 🙂
Expected behavior
I couldn't find a way to configure the extension to recognise the @ sign in the file paths.
Describe the bug
When I try opening a file with the
@
symbol in its path from the scan results, it fails, because@
gets encoded as%40
, and I get the "Unable to resolve nonexistent file" error -- see the screenshot.To Reproduce
Just have file paths containing the
@
in them 🙂Expected behavior
I couldn't find a way to configure the extension to recognise the
@
sign in the file paths.Screenshots
Versions
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: