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
Opening a terminal file link in VSCode terminal causes the file to be opened in the OS default application for the file type.
This leads to confusing behaviour where ctrl+click on the paths in a Rust error message files opens in VSCode but clicking the solution link opens in a different editor.
Possible solution could be detecting editors (like VSCode) which have their ow in path handling? sounds less than ideal...
Opening a terminal file link in VSCode terminal causes the file to be opened in the OS default application for the file type.
This leads to confusing behaviour where ctrl+click on the paths in a Rust error message files opens in VSCode but clicking the solution link opens in a different editor.
Possible solution could be detecting editors (like VSCode) which have their ow in path handling? sounds less than ideal...
example of this behaviour being odd to a user: https://www.twitch.tv/adrian_learns/clip/ArbitraryBoringPistachioPhilosoraptor-JJbB29pJTtQun9rS
The text was updated successfully, but these errors were encountered: