microsoft
Problems tab encoding problem
Type: Bug
In the Problems tab, a problem can be double-clicked to open the file at the problem's line of code. However, this does not work if the filename contains characters such as ä, ö, ü. The filename shows a diamond with a question mark for these characters (in the group header), which looks like the list is not using the proper encoding, hence it cannot open the file (message File not found).
VS Code version: Code 1.96.2 (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z) OS version: Windows_NT x64 10.0.22631 Modes:
Extensions (20)
| Extension | Author (truncated) | Version |
|---|---|---|
| mdoc | bxa | 1.4.0 |
| autoit | Dam | 1.0.12 |
| xml | Dot | 2.5.1 |
| rainbow-csv | mec | 3.14.0 |
| debugpy | ms- | 2024.14.0 |
| python | ms- | 2024.22.2 |
| vscode-pylance | ms- | 2024.12.1 |
| remote-wsl | ms- | 0.88.5 |
| powershell | ms- | 2024.4.0 |
| java | red | 1.38.0 |
| vscode-xml | red | 0.27.2 |
| tom | 1.2.2 | |
| intellicode-api-usage-examples | Vis | 0.2.9 |
| vscodeintellicode | Vis | 1.3.2 |
| vscode-gradle | vsc | 3.16.4 |
| vscode-java-debug | vsc | 0.58.1 |
| vscode-java-dependency | vsc | 0.24.1 |
| vscode-java-pack | vsc | 0.29.0 |
| vscode-java-test | vsc | 0.43.0 |
| vscode-maven | vsc | 0.44.0 |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
390bf810:31215807
6074i472:31201624
Note: using an english version of VS Code on a german version of Windows 11.
Sure:
- Create a source file with a name containing for example a ä
- Make sure there is a problem in the source file, such as using an undeclared variable (this depends off course on the language used, I see it while writing AutoIt scripts)
- The Problems panel shows the problem (in this case something like attempt to used undeclared variable)
- Double-click the Problem to open the source file at the line with the problem
Outcome: message File not found
Note that I'm using an English (US?) version of VS Code on a German version of Win11 Pro.
I hope that helps.
It seems to work for me. Can you please try following and let me know if it works
- Open Search view and search for the text that is there in that special file
- When the special file appears in the Search view, let me know if you can open the file from Search view?
It seems to work for me. Can you please try following and let me know if it works
- Open Search view and search for the text that is there in that special file
- When the special file appears in the Search view, let me know if you can open the file from Search view?
That works, so the Search view seems to use a different encoding for the file name.
This is what I get as the original error (below). When double-clicking the problem, Code tries to open a new file with the wrongly encoded file name, next to the original file with the correctly encoded file name. The file actually resides on OneDrive, but since that uses a local cache, I assume it's still a local file system based file (in C:\Users<username>\OneDrive).
I would say that the extension generating these problems is providing invalid file paths. I would recommend to file the issue against the extension and get it investigated there first.
I would say that the extension generating these problems is providing invalid file paths. I would recommend to file the issue against the extension and get it investigated there first.
Thanks, I've done that, let's see if the problem is indeed with the extension.