Searching in junction dir results in resolved path in results
In the "Search in Files" tab, when "Look in" is set to a directory that is a junction of a different directory on Windows, the results show from the resolved path instead of the file path relative to the junction directory.
To repo: 1. mkdir /j C:\someDir\someSubdir D:\myStuff\someSubdir_junction 2. Create a file with some text in the C:\someDir\someSubdir to search for. 3. In Wing, In the Search in Files tab, In Look In, set to "D:\myStuff\someSubdir_junction" 4. Search for the text in the file you added previously 5: See that the results show results with the C:\ paths, not the D: paths.
This causes issues when opening those files via double-clicking in the search results. It opens as an editor tab from the C-drive. When putting breakpoints in that editor window, if the D-drive paths are in PYTHONPATH or the env, those breakpoints don't get hit.
Comments