18 Apr
2005
18 Apr
'05
9:26 a.m.
Malcolm Wallace
I think runghc is acting like GHCi, and trying to read the file $HOME/.ghci on startup.
I toyed with this, and it seems like runghc is forking off a ghc process, which then tries to read .ghci (and possibly .inputrc) from the $HOME directory. Unfortunately, while runghc apparently parses -ignore-dot-ghci (i.e. it refuses illegal options), it later on seems to treat it's a source file to run. As far as I can tell. -kzm -- If I haven't seen further, it is by standing in the footprints of giants