The implementation in mainline cabal would be more general than what is currently in cabal-dev. The ticket (#382) mentions ghci but would ideally implement a 'cabal interact' command that opens whatever interpreter the user specifies (e.g. hugs instead of ghci). This would require some refactoring of the way cabal currently handles compiler options. On Thu, Mar 31, 2011 at 3:01 PM, Jason Dagit wrote:

On Thu, Mar 31, 2011 at 11:52 AM, Johan Tibell wrote:

...

On Thu, Mar 31, 2011 at 8:33 PM, Frank Murphy wrote:

...

What do people think about seeing this ticket (#212) resolved as part of a SoC project? Is it worthwhile enough to merit consideration?

It might be too small a task to cover the whole summer, depending on the scope you pick. You could combine it with some other tasks, like implementing "cabal ghci" support or some other "Hard" task for the bug tracker.

I've seen a few people requesting 'cabal ghci' lately, and I just want to point out that cabal-dev already has a ghci command.  I use it quite often and it's been working well for me. Jason

On 31 March 2011 20:22, Johan Tibell wrote:

On Thu, Mar 31, 2011 at 9:01 PM, Jason Dagit wrote:

...

I've seen a few people requesting 'cabal ghci' lately, and I just want to point out that cabal-dev already has a ghci command.  I use it quite often and it's been working well for me.

Right. We've been talking about merging the cabal-dev functionality into cabal. Just the cabal ghci part should be doable in a week (there's a ticket for it).

There's not only a ticket, there's a patch! I implemented this donkeys years ago but in the "wrong part" of Cabal (Cabal library instead of cabal-install, or vice-versa) so it never got applied :( The patch took me a few hours last time (with no prior Cabal knowledge) so it should certainly be doable in a week. Max