Skip to content

FAQ

Jump to bottom
Jerome Lelong edited this page Dec 23, 2018 · 147 revisions

FAQ and common issues

Known incompatible Extensions

The following extensions are known to cause issues when active at the same time as LaTeX-Workshop, namely a significant delay when using the Enter key in large files.

The Problem Pane displays wrong messages

LaTeX compilers usually produce hard wrapped log messages, which makes them really hard to parse. To hopefully deal with complex log messages, we have decided to rely on non hard wrapped log messages. This can be achieved either

  • by setting the environment variable max_print_line. This is automatically done within the extension and works for the TeXLive distribution.
  • by adding the --max-print-line option to the compilers. This is automatically done within the extension and works for the MiKTeX distribution. Unfortunately, some compilers such as lualatex or xelatex do not understand this option and may therefore fail. To disable the automatic addition of this option, set latex-workshop.latex.option.maxPrintLine.enabled to false.

Note that when log messages are hard wrapped, the Problems Pane may be messed up.

I cannot use ctrl+alt in a shortcut

The default shortcuts for commands related to build and view use the modifiers ctrl+alt. On some keyboard layouts, ctrl+alt is used to emulate AltrGr, which makes these shortcuts unusable. Alternatively, you can use ctrl+l, alt+letter instead of ctrl+alt+letter by setting latex-workshop.bind.altKeymap.enabled to true (you need reload/reopen vscode for the change to be taken into account).

Disable automatic build on save

Set the configuration variable latex-workshop.latex.autoBuild.onSave.enabled to false.

My file is built when I paste

Set editor.formatOnPaste to false.

The formatting program latexindent changes the file on disk when formatting and not only the buffer content. VSCode interprets it as a file save and triggers a build if latex-workshop.latex.autoBuild.onSave.enabled to true

Format on save does not work

This is a known issue but we cannot do much from the extension side.

The formatting utility latexindent reads its input from the file on the disk and not from the content of the editor. So when using Format on Save, first you format the file on the disk and then you save the content of the buffer. This is obviously done in the wrong order, but we cannot do much from the extension side to fix this. Note that if you save twice, the editor content is indeed formatted. When using RightClick->Format Document, we first save the buffer before calling the formatting program.

My file gets messed up

This is most likely related to the two following variables being set together latex-workshop.latex.autoBuild.onTexChange.enabled: true and editor.formatOnSave: true.

Formatting a .tex file actually changes it on the disk and then if latex-workshop.latex.autoBuild.onTexChange.enabled is true it saves the file and triggers a build. You will get two formatting processes running together and using the same temporary file. Hence, the mess you see in your file.

Large bibtex files are ignored

Bibtex files listed in a project are parsed for citation completion. This may induce significant slow down with large bibtex files. You can configure the maximum size of bibtex files parsed by the extension with latex-workshop​.intellisense​.citation​.maxfilesizeMB".

Path containing Chinese characters

On some platforms, when the path of a TeX file contains Chinese characters or other non-ASCII characters, the compilation does not work well. In such cases, please use %DOCFILE% instead of %DOC% in your recipes. See also LaTeX recipe.

On some platforms, synctex doesn't work well with the path containing non-ASCII characters either. In such cases, please use a built-in synctex functionality. See Viewing & Synctex.

Want to contribute to this Wiki?

Fork it and send a pull request.

Table of Contents

Clone this wiki locally