We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I've found that => doesn't replaced with ligature for Scala code in lstlisting. E.g.
=>
lstlisting
\documentclass{article} \usepackage{fontspec} \setmonofont{FiraCode-Regular.otf}[ BoldFont=FiraCode-Bold.otf, Contextuals=Alternate% Activate the calt feature ] \usepackage{xcolor} \usepackage{listings} \usepackage[verbatim]{lstfiracode}% Activate ligatures in verbatim \lstset{ language=scala, style=FiraCodeStyle,% Use predefined FiraCodeStyle basicstyle=\ttfamily,% Use \ttfamily for source code listings commentstyle=\color{orange} } \begin{document} \begin{lstlisting} object Main extends App { println("Hello world") def foo(lst: List[String]) = { lst.sortBy((a, b) => a >= b) } } \end{lstlisting} \end{document}
I suppose it's because => is defined as keyword in lstlisting for Scala
The text was updated successfully, but these errors were encountered:
@limansky You are probably right. I will need to figure out something to override the language=scala setting.
language=scala
Sorry, something went wrong.
I wish it still would have a color and font weight defined for keywords, but printed as a ligature.
No branches or pull requests
Hi,
I've found that
=>
doesn't replaced with ligature for Scala code inlstlisting
. E.g.I suppose it's because
=>
is defined as keyword inlstlisting
for ScalaThe text was updated successfully, but these errors were encountered: