Ask Your Question

Searching in junction dir results in resolved path in results

asked 2022-01-28 11:15:55 -0500

Ben's avatar

updated 2022-05-05 09:32:25 -0500

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.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2022-01-31 11:35:44 -0500

Thanks for this bug report. We'll look at improving this.

edit flag offensive delete link more


There's a fix for this going into our next update ( I'm not sure yet when that will be pushed out, but we usually issue updates every two weeks.

Wingware Support's avatar Wingware Support  ( 2022-02-07 09:12:50 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2022-01-28 11:15:55 -0500

Seen: 129 times

Last updated: Feb 20 '22