<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<!-- Generated by HsColour, http://www.cs.york.ac.uk/fp/darcs/hscolour/ -->
<title>src/Imogen/Infon/Fol/Subst.lhs</title>
<link type='text/css' rel='stylesheet' href='hscolour.css' />
</head>
<body>
The files now don't have this header, and they are not showing up colored.
Second, I'm probably being a pain in the ass, but I'd also like to keep my literate comments
preformatted. Right now they are mashed all together and are unreadable. Would it be possible
to add an option for preformatting, in case you prefer the default to be unformatted?
Thanks!
Sean
On Fri, Aug 21, 2009 at 6:24 AM, Malcolm Wallace <Malcolm.Wallace@cs.york.ac.uk> wrote:
I've fixed hscolour - from the newly release version 1.14 there is now no difference between the -lit and -lit-tex options. Both will deal with either style of literate input.The annoying thing here is that to "do the right thing" Cabal would need
to distinguish bird-track style literate files (hscolour -lit) from tex
style (hscolour -lit-tex). I don't think this is reasonable.
Hscolour-1.14 also makes this fix. If your source file name ends in .lhs or .ly or .lx, it will be automatically processed with -lit. You can override the guess, by using an explicit -nolit (or -lit) to force the particular behaviour you want.
It might be worth asking if hscolour should by
default just do the right thing, ie use -lit on .lhs input files.
Another new change, is that you can now supply multiple filenames as input, and their colourised contents will be concatenated to the output.
Regards,
Malcolm
_______________________________________________
Libraries mailing list
Libraries@haskell.org
http://www.haskell.org/mailman/listinfo/libraries