-
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 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 can compile it with the exact same binary and options. Describe the bug [Required]
I have the strong suspicion that it has to do with the fact that To ReproduceSteps to reproduce the behavior:
Expected behaviorThings compile. Progress indicator does not get stuck indefinitely. Logs [Required]Latex Workshop Compiler Output
NOTE: it is entirely stuck after outputting those two asterisks ( LaTeX Workshop Output [Required]
Developer Tools Console [Required]Nothing here, except for a warning that VSCode has been showing since forever:
Screenshots(none) Desktop [Required]Please write exact version numbers. Please don't write
Additional questionsAre 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 Additional contextI think it is worth noting that Latex Workshop has been getting stuck all the time, but ONLY IF the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I feel that the extension should better deal with issues of configuration that lead to interactive mode to get the compiler stuck indefinitely... Why not force close or at least show a WARNING, if It gets stuck A LOT, in all kinds of scenarios. |
Beta Was this translation helpful? Give feedback.
OPTIONS
are invalid (missing%DOC%
), and it thus drops into interactive mode, waiting for the file to be provided.I feel that the extension should better deal with issues of configuration that lead to interactive mode to get the compiler stuck indefinitely... Why not force close or at least show a WARNING, if
stdin
opens up or is getting read from?It gets stuck A LOT, in all kinds of scenarios.