Changes between Initial Version and Version 1 of Ticket #3140


Ignore:
Timestamp:
May 23, 2009 7:44:09 PM (6 years ago)
Author:
igloo
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3140

    • Property Difficulty changed from to Unknown
  • Ticket #3140 – Description

    initial v1  
    11On 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: 
    22 
    3 * Create file `Foo\Bar.hs` containing a module `Foo.Bar` that imports `Foo.Baz`. 
    4 * Create file `Foo\Baz.hs` containing a module `Foo.Baz`. 
    5 * Double-click on `Foo\Bar.hs`; GHCi whines that it can't find `Foo.Baz` in the search path. 
     3 * Create file `Foo\Bar.hs` containing a module `Foo.Bar` that imports `Foo.Baz`. 
     4 * Create file `Foo\Baz.hs` containing a module `Foo.Baz`. 
     5 * Double-click on `Foo\Bar.hs`; GHCi whines that it can't find `Foo.Baz` in the search path. 
    66 
    77This 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.