Comments on: Colors in GHCi

By: Martijn

Martijn — Thu, 24 Jun 2010 09:24:03 +0000

@Orphi Yes, I agree. It shouldn’t be too hard.

@Nikolas Good question. I have no good reason for it.

By: Nikolas Mayr

Nikolas Mayr — Wed, 03 Mar 2010 13:39:18 +0000

Why are you using

#!/usr/bin/env bash

intead of

#!/bin/bash

By: Orphi

Orphi — Mon, 01 Mar 2010 11:59:37 +0000

I still think GHCi should have this built-in. We already have ansi-terminal on Hackage, which does this in a [ahem] *portable* way. (Your examples don’t work on Windows, because it fails to grok ANSI escape sequences.)

By: Erlend

Erlend — Sat, 27 Feb 2010 18:12:54 +0000

Cool. Thanks!
Works perfectly on openSuse 11.2.

By: Tom Lokhorst

Tom Lokhorst — Sat, 27 Feb 2010 16:26:56 +0000

This is very useful!

I’ve updated the script to also highlight warnings (as I usually launch ghci from vim with -Wall):

#!/usr/bin/env bash

YELLOW=`echo -e ‘33[93m’`
GREEN=`echo -e ‘33[92m’`
RED=`echo -e ‘33[91m’`
RESET=`echo -e ‘33[0m’`

/usr/bin/ghci “${@}” 2>&1 |\
sed “s/ Warning:/${YELLOW}&${RESET}/g;s/^Failed, modules loaded:/${RED}&${RESET}/g;s/^Ok, modules loaded:/${GREEN}&${RESET}/g”

I’m not happy with the fact that this merges the stdout and stderr, but I don’t know of a better way to do this.