Currently the extension does not allow line commenting.

This can be easily fixed though. Please consider this pull request.

Something looks wrong with lstlisting environment, just like this:

The \begin{...} and \end{...} can't match. Only when using lstlisting, it will happen.

Is it possible to add a snippet to the extension that gets invoked inside a tasks.json file and shows a basic latex->pdf compilation task, with configurations for mac, linux and windows (MikTex) and a problem matcher (comparable to the experience in TexStudio)?

Currently, only a small number of LaTeX commands are highlighted. However, in TeX, any token starting with \ is a command. So all of these tokens should be highlighted. Currently, they appear to be text content.

Examples of common LaTeX commands not being highlighted:

• \setlength
• \parbox
• \vfill
• \paperwidth
• \makeatletter

… and so on. It does not seem to be feasible to include all LaTeX commands in the extension, so it should simply highlight all TeX commands. This also would make the bundle more useful for:

• plain TeX
• ConTeXt

Apologies for the delay here - as we have been working hard away at the core of VS Code this extension has gotten very little love. In part as the community has really stepped up and provided far better LaTeX support.

As a result of this I just pushed and update deprecating this extension in favor of a community alternative which I suggest you use LaTeX Workshop.

Again sorry for the radio silence here and we hope this will provide you with a much better experience moving forward. For now I'm closing any open issues and PRs as this extension is no longer under active development.

Sean - VS Code team member

The extension doesn't support default themes: Light+, Dark+.

• highlighting of several LaTex commands in default theme
• highlighting of user defined macros in default theme

1. Is it possible to automatically close brackets while typing {?
2. There is a LaTex Beamer.plist in latex.tmbundle

Thanks.

Apologies for introducing two separate issues at once.

I am on VSCode v1.8, plugin v0.1.3, OSX (Sierra).

When I type eq<TAB>, I get

\begin{equation}
<cursor>
\end{equation}

as expected.

However, when I type ali<TAB>, I get

<cursor>\begin{align`echo TM_SCOPE|grep math|
sed -e 's/.*math.*/ed/'`}

\end{align`echo TM_SCOPE|grep math|
sed -e 's/.*math.*/ed/'`}

This aberrant behavior also crops up in the snippet for new environment. Typing begin<TAB> gives

\begin{env}
  \item )(?2:\item)/
\end{env}

I have not extensively tested all snippets; these are just the ones I happened to observe.

Secondly, please introduce autocompletion for labels (inserting references to equations, subequations, figures and tables). MWE:

\begin{equation}
\label{eq:test_eq_1}
x = a + b
\end{equation}

Using equation \ref{eq:<TAB>}

Here one hopes that the editor suggests relevant labels for completion.

Referring to this line and its double-quote buddy: https://github.com/Microsoft/vscode-LaTeX/blob/master/syntaxes/latex.tmLanguage#L1628

Is there a reason that quoted strings preceded by whitespace are considered to be illegal? They seem to be perfectly valid in pdflatex, but perhaps I've missed something :)

This is particularly frustrating in this theme I'm using (which I appreciate isn't your responsibility), which has a bug making all "invalid.illegal" tokens invisible:

Forgive me if this isn't the right place to ask!

VSCode 1.3.1
LaTeX 0.1.1

As the title says, $ $ for an inline equation does not get highlighted.