Skip to content

windows installer should play nice with other Haskell tools

traditionally, the windows installers have registered ghci as the default tool to operate on .hs/.lhs files, without regard for existing file type associations. that has been a real pain for those of us who like to use many tools on haskell files.

could you please ensure that future installers are more cooperative?

  • coordinate with Neil for WinHugs, and possibly with others
  • make file type registration optional
  • do not overwrite existing default handler for .hs/.lhs, just add new non-default handlers (so people can use their own defaults, eg. editors, and still have easy access to ghci, hugs, ..)

this has come up many times. see also:

http://www.haskell.org/pipermail/glasgow-haskell-users/2004-March/006402.html http://www.haskell.org/pipermail/hugs-users/2006-February/000656.html http://article.gmane.org/gmane.comp.lang.haskell.cvs.ghc/14819/ http://www.haskell.org/pipermail/glasgow-haskell-users/2006-September/011107.html http://www.haskell.org/pipermail/glasgow-haskell-users/2006-September/011110.html

Trac metadata
Trac field Value
Version 6.4.2
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component GHCi
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture Unknown
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information