-
Notifications
You must be signed in to change notification settings - Fork 535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems Window refers to a nonexistent file if the file path has special characters (space, etc.) #784
Comments
It's mostly LaTeX's problem. If not, please provide minimal workinh example. |
I'm unsure what would be a minimal working example here. Do you want a test file in a test folder? The only 2 requirements to reproduce the issue is that the file has to have some kind of compiling errors or warnings, and the path to the file has to have some spacing characters. |
I think this might be the same as what I reported in #786 (and is now fixed in the source) |
@philipstarkey, yes it is indeed the same problem. I'm glad your "version" of the same problem got chosen to be fixed! ;-) |
Hi, I'm new to VS Code. I installed the LW extension and this problem with special characters still persists. I have 1.28.2 VS Code version. I tried it with 1.25 version and the error message dissapears, however it still doesn't show me the line with the problem. |
Description
File path is not recognized in the PROBLEM window if there are spaces or special characters. Therefore, you can't click on a warning to get to the right line.
Log messages
No log error / not applicable
How to reproduce
Expected behavior
The problems should show up in the PROBLEMS window. They should be clickable, and clicking them shows the line with the error/warning.
Actual behavior
The problems will show up, but under a nonexistent file path, which gets cut off because of the special characters. Clicking on any problem will show an error notification popup saying "Unable to open...: File not found" with the truncated path.
The text was updated successfully, but these errors were encountered: