On Tue, Apr 17, 2012 at 12:11 AM, Vinay Sajip
<vinay_sajip@yahoo.co.uk> wrote:
Thanks, but that link just leads either to answers saying it can't be done, or
information about using assoc and ftype to associate e.g. .hs files with
runhaskell. That's not the crux of the problem: the crux is that runhaskell on
Linux will run .hs files with a #!/usr/bin/env runhaskell (even though that's
not a valid line in Haskell), whereas runhaskell.exe on Windows will try to
parse that first line using the Haskell parser, even though it's not valid
Haskell (the Linux version presumably skips that first line).