-
Notifications
You must be signed in to change notification settings - Fork 527
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
Can not show error if file name has spaces. #3311
Comments
I cannot reproduce the issue. |
Untitled 1.txt |
Unfortunately, I cannot reproduce the issue with your example. Could you post the output of the LaTex compiler in both cases? |
When file name is Untitled 1.tex
It seems only file name changed in both log files and in some places the name with space are quoted. |
I have found the difference. Compare the two outputs
and
Notice that there is no line break after
Yet, I am puzzled by all this because with exactly the same versions of |
This comment was marked as off-topic.
This comment was marked as off-topic.
The same problem occurs in another PC of my friend. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
The log parser is a little fragile so before tweaking it I would like to understand how this is happening.
|
I tried Miktex the problem disappeared. |
@James-Yu Can you reproduce the issue using TeX Live on Windows? |
We can see the cause of the difference, #ifdef W32UPTEXSYNCTEX
{
char *stmp = chgto_oem(tmp);
printf((synctex_ctxt.flags.quoted ? "SyncTeX written on \"%s\"\n" : "\nSyncTeX written on %s.\n"),
stmp);
free(stmp);
}
#else |
@tamuratak Thanks for the reference. This is exactly what I was looking for. Yet, these lines have not been changed for 5 years. I do not understand why we have not faced this issue earlier. I am not sure this is worth reporting an issue at tug.org by writing to the |
@jlelong As I said before, you can try using a LaTeX log parser implemented with PEG.js You can execute Since I am not interested in adding tweaks to the parser on my side, it would be better to extract the parser to a new repository if you are interested. Notice that the PEG.js project is not active. It might not be a good idea to start developing a new parser with PEG.js. |
All in all, I am not interested in developing a new warning / error parser using I have posted to the |
I see. |
It has just been fixed in TeX-Live/texlive-source@244cf99 So, I am closing the issue as everything is expected to just work fine with the next release of TeX Live. |
Preliminary questions [Required]
Disable all the other extensions except for LaTeX Workshop, restart VS Code, and check that you still see this issue. [Required]
You still see this issue?: Yes/No
Make sure to visit the wiki FAQ before filling an issue.
You visited the wiki?: Yes
If your issue is with compiling a document (not having to do with finding the root file of a project), check first that you can compile manually.
You can compile a TeX document manually?: Yes
Describe the bug [Required]
If the tex file name has space, Latex-Workshop can not present the syntax error in problem panels. For example, I use \acute{a} in text without math mode. I need to check log file to find the reason why the recipe terminated with error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Logs [Required]
Please paste the whole log messages here, not parts of ones. The log should start with
Initializing LaTeX Workshop
. It is very important to identify problems.LaTeX Workshop Output [Required]
Developer Tools Console [Required]
To access the log, click 'help' -> 'Toggle Developer Tools' -> 'Console'. Paste anything suspicious.
Nothing
Screenshots
Desktop [Required]
Please write exact version numbers. Please don't write
latest
instead of exact numbers.Additional questions
Are you using VSCodium?
No
Are you using the Snap or Flatpack versions of VS Code?
No
Are you using LaTeX Workshop with VS Code Remote?
No
If the answer is Yes, please write which one you are using. Write the versions of the remote extension.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: