You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this case, only the const keyword is being highlighted. It seems like only generic keywords that could apply to many languages are being highlighted.
I'm building with the docker container using these parameters:
--template eisvogel --listings
Do I need to pass in specific definitions for JavaScript?
The text was updated successfully, but these errors were encountered:
You can omit the option --listings to use the pandoc default syntax highlighting, which has definitions for JavaScript.
Markdown Input
~~~ {.js}
var a = "Alpha"
const b = "Beta"
let c = "Gamma"
~~~
~~~ {.sql}
CREATE TYPE person_t AS (
firstName VARCHAR(50) NOT NULL,
lastName VARCHAR(50) NOT NULL
);
~~~
LaTeX Output with Option --listings
\begin{lstlisting}
var a = "Alpha"
const b = "Beta"
let c = "Gamma"
\end{lstlisting}
\begin{lstlisting}[language=SQL]
CREATE TYPE person_t AS (
firstName VARCHAR(50) NOT NULL,
lastName VARCHAR(50) NOT NULL
);
\end{lstlisting}
You can see the first code block is missing a language because pandoc knows that listings doesn't support javascript. The default highlighting of Java is applied.
LaTeX Output without Option --listings (uses skylighting)
JavaScript keywords are not all being highlighted for blocks like this:
~~~
In this case, only the const keyword is being highlighted. It seems like only generic keywords that could apply to many languages are being highlighted.
I'm building with the docker container using these parameters:
Do I need to pass in specific definitions for JavaScript?
The text was updated successfully, but these errors were encountered: