Open File from Cmd Pallette Uses Partial Path while Open from Search Results Uses Full Path

[jkassis]

When I open a file using the command palette, it recognizes that the file is relative to my document root.

When I open the file using search results from workspace-wide search, it opens with the full path.

The file opened by search results is then disconnected from the projects... code navigation commands don't work. SETTING BREAKPOINTS DONT WORK. Note that this could explain why some of the breakpoints not working tickets are hard to track down. It may have nothing to do with symlinks.

[jkassis]

@ramya-rao-a ^^^ Maybe explains why debugger breakpoints don't work sometimes.

[jkassis]

more...

[jkassis]

maybe vscode needs a special system-wide cap-safe mode for osx?

[bpasero]

I think quick open does the right thing but search does not, moving to Rob.

[roblourens]

Hm, basically you search in folder foo and find file bar and we return foo/bar, there is no case-normalization step. Quickopen would normally do the right thing if Code was opened with the correctly cased workspace folder. But @bpasero I can reproduce the same thing with quickopen's absolute path handling logic -

mkdir Foo
touch Foo/bar

then in quickopen, open ~/folder/Foo/bar and ~/folder/foo/bar, and they open as separate tabs with differently cased paths. As far as I know we don't really do any case normalization anywhere in vscode and this would fall under the master path case issue that we have.

[bpasero]

If that is the issue, then it is #12448