[Tex/LaTex] Highlighting haskell listings in large *.tex document

beamerlistingstex-core

Suppose, there is a large *.tex document, which has many nested \input directives with many Haskell listings surrounded by \begin{code} \end{code}
commands.

How can all this code listings be highlighted like all haskell code is highlighted in many haskell papers (functional pearls is a good example)?

I heard, that many haskell papers written in lhs and then transferred to tex via lhs2tex. Yep, this is a nice tool, but it produces whole tex document and it is hard to be usable for the task like mine.

Btw, I've tried lstlistings and fancyvrb – it's far away from ideal.

Best Answer

I was pleased with my lstlistings setup which I used in my bachelor thesis:

\lstset{
  frame=none,
  xleftmargin=2pt,
  stepnumber=1,
  numbers=left,
  numbersep=5pt,
  numberstyle=\ttfamily\tiny\color[gray]{0.3},
  belowcaptionskip=\bigskipamount,
  captionpos=b,
  escapeinside={*'}{'*},
  language=haskell,
  tabsize=2,
  emphstyle={\bf},
  commentstyle=\it,
  stringstyle=\mdseries\rmfamily,
  showspaces=false,
  keywordstyle=\bfseries\rmfamily,
  columns=flexible,
  basicstyle=\small\sffamily,
  showstringspaces=false,
  morecomment=[l]\%,
}

You can find some examples in my thesis: https://www.dropbox.com/sh/zu56xcp1mj57ikq/TtFoHKmOLV/thesis.pdf

I can also provide the whole .tex source if needed.

Related Solutions

[Tex/LaTex] Problem highlighting listings in beamer

Better late than never :)

As stated by Qrrbrbirlbel in his comment, the problem is that, because % is a (one-line) comment delimiter in the Octave language, listings treats your closing overlay delimiter @ as part of the comment.

One workaround is to undefine % as a comment delimiter, but use literate to apply the comment style when that character is encountered anyway. You also need to reset the style at the beginning of each line.

enter image description here

Two caveats of this approach:

any % character that occurs within a string literal will mess up the highlighting,
keywords get highlighted even in comments.

\documentclass[dvipsnames,cmyk]{beamer}

\usepackage{arev}
\usepackage{listings}

% remove navigation symbols 
\setbeamertemplate{navigation symbols}{}

\lstdefinestyle{highlight}{
  keywordstyle=\color{red},
  commentstyle=\color{green},
}

\makeatletter

\lstdefinestyle{base}{
    language      = Octave,
    emptylines    = 1,
    breaklines    = true,
    basicstyle    = \tiny\ttfamily\color{black!40},
    keywordstyle  = \color{red!40},
    commentstyle  =\color{green!40},
    moredelim     = **[is][\only<+>{\color{black}\lstset{style=highlight}}]{@}{@},
    %
    % Undefine % as a comment delimiter, but still apply comment style when it's encountered.
    deletecomment =[l]\%,
    literate      ={\%}{{\lst@commentstyle\%}}1,
}

% Reset the style at the beginning of every ``true'' line
\lst@AddToHook{EveryPar}{\lst@basicstyle}

\makeatother

\begin{document}
\begin{frame}[fragile]%{Listings overlay}

\begin{lstlisting}[style=base, gobble=0]
@% This comment will be highlighted; it is also bigger than the frame size so it is expected that line is breaked into at least two. Note that unwanted empty line may be generated
@

@a = 2@ % aaa
@b = 1 % aaa @
@c = 1 % aaa @
@d = 1 % aaa @

\end{lstlisting}

\end{frame}
\end{document}

[Tex/LaTex] Listings: text highlighting based on prefix

Here is one way of doing it using moredelim. I assumed you meant words starting with op-, not words starting with cp-. I didn't use keywordsprefix because it currently only allows for one prefix "class", and the listings documentation (v1.5b) still considers it a buggy feature; see subsection 4.18 about that.

Remember to load lmodern if you want some stuff to be typeset in bold typewriter font.