First time here? Check out the FAQ!
1

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.

Ben's avatar
11
Ben
asked 2022-01-28 11:15:55 -0500
Wingware Support's avatar
4.1k
Wingware Support
updated 2022-05-05 09:32:25 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

0

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

Wingware Support's avatar
4.1k
Wingware Support
answered 2022-01-31 11:35:44 -0500
edit flag offensive 0 remove flag delete link

Comments

There's a fix for this going into our next update (8.1.3.1). 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
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer