Opened 9 years ago

Closed 22 months ago

#3140 closed feature request (duplicate)

(Windows?) GHCi doesn't load hierachical modules

Reported by: Orphi Owned by:
Priority: lowest Milestone: 8.0.1
Component: GHCi Version: 6.10.1
Keywords: Cc:
Operating System: Windows Architecture: x86
Type of failure: None/Unknown Test Case:
Blocked By: Blocking:
Related Tickets: #10643 Differential Rev(s):
Wiki Page:

Description (last modified by igloo)

On Windows, if you double-click a *.hs file, GHCi starts up and loads the corresponding module. Usually this works fine, however... it seems to trip over on hierachical module names. Specifically:

  • Create file Foo\Bar.hs containing a module Foo.Bar that imports Foo.Baz.
  • Create file Foo\Baz.hs containing a module Foo.Baz.
  • Double-click on Foo\Bar.hs; GHCi whines that it can't find Foo.Baz in the search path.

This happens regardless of whether either of the modules is compiled or not. An easy work-around is to invoke GHCi from the command prompt with the CWD below the Foo folder. But it's kind of tedious to have to do that.

Note that if Foo.Bar doesn't import anything (or only modules from packages) then it works just fine. GHCi just doesn't seem to be able to find source files in the current folder if they have hierachical names.

Change History (14)

comment:1 Changed 8 years ago by igloo

Description: modified (diff)
difficulty: Unknown

comment:2 Changed 8 years ago by igloo

Milestone: 6.12 branch
Type: bugfeature request

Thanks for the suggestion.

comment:3 Changed 7 years ago by igloo

Milestone: 6.12 branch6.12.3

comment:4 Changed 7 years ago by igloo

Milestone: 6.12.36.14.1
Priority: normallow

comment:5 Changed 7 years ago by igloo

Milestone: 7.0.17.0.2

comment:6 Changed 7 years ago by igloo

Milestone: 7.0.27.2.1

comment:7 Changed 6 years ago by igloo

Milestone: 7.2.17.4.1

comment:8 Changed 6 years ago by igloo

Milestone: 7.4.17.6.1
Priority: lowlowest

comment:9 Changed 5 years ago by igloo

Milestone: 7.6.17.6.2

comment:10 Changed 3 years ago by thoughtpolice

Milestone: 7.6.27.10.1

Moving to 7.10.1.

comment:11 Changed 3 years ago by thoughtpolice

Milestone: 7.10.17.12.1

Moving to 7.12.1 milestone; if you feel this is an error and should be addressed sooner, please move it back to the 7.10.1 milestone.

comment:12 Changed 3 years ago by thoughtpolice

Moving to 7.12.1 milestone; if you feel this is an error and should be addressed sooner, please move it back to the 7.10.1 milestone.

comment:13 Changed 2 years ago by thoughtpolice

Milestone: 7.12.18.0.1

Milestone renamed

comment:14 Changed 22 months ago by thomie

Resolution: duplicate
Status: newclosed
Type of failure: None/Unknown

This was brought up again recently in #10643, which has more discussion, so I'll close this one as a duplicate.

Note: See TracTickets for help on using tickets.