Replies: 2 comments
-
|
The issue is not related to the extension. You should fix each error in the output of |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
You have errors in your |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Preliminary questions [Required]
Disable all the other extensions except for LaTeX Workshop, and check that you still see this issue. [Required]
You still see this issue?: Yes
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
I am also using Sublime Text 3 with latextool.
Describe the bug [Required]
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
I am expecting to initiate a single recipe that would compile without any interruptions. In other format like: IEEE trans, it works out of the box using pdf->bib->pdf->pdf.
A clear and concise description of what the bug is.
Hi,
I am having problem compiling my thesis that is initially downloaded from Here.
I am not sure whether it is a bug or not. Most likely it can be the latex formatting issue from the styling format that I am using. But then my question, why it works within a single command when I am running the same file under SublimeText but it does not happenning within vscode. I do not have issue compiling other format like IEEE trans, elsevier. However, I did face similar issue like the above while trying to compile acm class. The main problem lies dealing with the bib/bibtex (most probably, my guess).
I am using the following recipe to build and compile
{ "name": "xelatex", "command": "xelatex", "args": [ "-synctex=1", "-interaction=nonstopmode", "-file-line-error", "%DOCFILE%" ] }, { "name": "xe->bib->xe->xe", "tools": [ "xelatex", "bibtex", "xelatex", "xelatex" ] }, { "name": "xe->xe", "tools": [ "xelatex", "xelatex" ] }, { "name": "xelatex", "tools": [ "xelatex" ] }The weird part to me is that: If I use the latextool from within sublime text 3, it works out of the box with the necessary citation and other things like figures, tables. However, when it comes to build (or compile inside vscode) then it does not work within a single command (or recipe). The technique that I use to make it work is that:
Step 1: xe->bib->xe->xe (The build process stops after issues warnings)
Step 2: xe->xe (The build finally success)
Most likely the problem is happening due to the management of bibtex (*.bib).
(Step-1 ) The PDF generates though as Output successfully but the Reference Section does not shows up and in the text it shows [?] before the sentence.
But I am still not sure what causes the problem and how can I find a single recipe that would work out of the box with a single command.
I have tried to combine the above two builds using xe->bib->xe->xe-xe->xe but still the interruptions happen. Any advice or ideas on recipe customization would be really appreciated from the community.
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]
Step 1: xe->bib->xe->xe (The built process interrupted) (477 warnings, 16 infos)
Step 2: xe->xe (build successes) 8 warnings 24 infos
To access the log, click the 'TeX' icon on the Activity Bar on the left side, select 'View Log Messages', then select 'View LaTeX Workshop extension log'.
[Paste the log here]
Step 1: xe->bib->xe->xe (The built process interrupted) (477 warnings, 16 infos)
Step 2: xe->xe (Builds successfully) 8 warnings 24 infos
Developer Tools Console [Required]
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop [Required]
Additional questions
Are you using VSCodium?
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.
Beta Was this translation helpful? Give feedback.
All reactions