-
Notifications
You must be signed in to change notification settings - Fork 697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cabal repl and the Paths_mypackage module #1842
Comments
Just to say that As a temporary work around you can set the enviroment variable $ export <mypackage>_datadir=$PWD
$ cabal repl or $ <mypackage>_datadir=$PWD cabal repl (replace |
I just tried this out, and it's now pointing at the directory in my sandbox where |
The trick works for cc @kmicklas |
cabal repl switches current directory for subpackages of a project, resulting in error paths relative to some subdirectory. This confuses downstream tooling. Related cabal tickets are haskell/cabal#5001 haskell/cabal#1842 Gated behind the newly added flag --force-absolute-paths
cabal repl switches current directory for subpackages of a project, resulting in error paths relative to some subdirectory. This confuses downstream tooling. Related cabal tickets are haskell/cabal#5001 haskell/cabal#1842 Gated behind the newly added flag --force-absolute-paths
cabal repl switches current directory for subpackages of a project, resulting in error paths relative to some subdirectory. This confuses downstream tooling. Related cabal tickets are haskell/cabal#5001 haskell/cabal#1842 Gated behind the newly added flag --force-absolute-paths
cabal repl switches current directory for subpackages of a project, resulting in error paths relative to some subdirectory. This confuses downstream tooling. Related cabal tickets are haskell/cabal#5001 haskell/cabal#1842 Gated behind the newly added flag --force-absolute-paths
cabal repl switches current directory for subpackages of a project, resulting in error paths relative to some subdirectory. This confuses downstream tooling. Related cabal tickets are haskell/cabal#5001 haskell/cabal#1842 Gated behind the newly added flag --force-absolute-paths
I'm not sure if this is intended behavior, but I'd expect the
Paths_<mypackage>
module to point somewhere meaningful when I'm running incabal repl
. It seems to point to my user directory when I'd expect it to point to the current package root.The text was updated successfully, but these errors were encountered: