# Minted's Haskell syntax coloring seems incorrect

The output of the following source code has the first fmap colored in blue (I think it's the keyword coloring) and the second in black (which should be "no coloring" for normal variable names).

\documentclass{standalone}
\usepackage{minted}
\begin{document}

I've also noticed that if the second argument to \mintinline is a -> b, the a is colored in blue.
Does this mean there's something that could be fixed in the package and that I can send an e-mail to the author, or is it this the expected behavior because the package only colors "valid" haskell code? (For instance, a line only containing fmap . fmap is indeed invalid, as far as I can tell.)
• well, minted doesn't do the syntax highlighting itself – it uses the excellent Python Pygments library / pygmentize tool. When you run pygmentize -l haskell sourceode.hs with your code in a file, is the result as you expect it? Mar 15 at 21:29
• @MarcusMüller well, i understand that it can't parse code syntactically incorrect. But fmap . fmap is syntactically correct, I think. As in, it is correct code if it's for instance in f = fmap . fmap. Mar 15 at 21:55
• no, fmap . fmap is not correct haskell, while f = fmap . fmap is. (ask your haskell compiler!) Mar 15 at 22:06