Providing a smooth default user experience
sol at typeful.net
Fri Nov 2 11:25:11 CET 2012
> Recently, I had to add a MIN_VERSION macro to my code because of the
> old-time / time change in directory, but couldn't test the library in
> ghci because the macro was not defined.
> I discovered that configuring ghci with
> :set -optP-include -optPdist/build/autogen/cabal_macros.h
> tells ghci about the macro, but I find this even more cumbersome than
> So, if I'm not missing something, it may also be comfortable to add a
> cabal ghci
> command which tells ghci about cabal's configuration.
You can put the required options in a .ghci file in you project root. I
use  as a starting point for new projects,  and  are real world
`cabal ghci` could still be useful, but I think a general solution is
not trivial. It would probably need to accept qualified targets, e.g.
`ghci test:properties` to start ghci in a way suitable for a test-suite
with the name "properties".
Moreover, it would be awesome if it would regenerate generated source
files on :reload. I'm not sure if this is feasible without changes to
GHCi, but a custom macro, e.g.
could still work.
More information about the cabal-devel