Skip to content
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.

Sign up for GitHub

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

Document that stack ghci works best only after stack build. #4180

Merged
merged 1 commit into from
Jul 28, 2018
Merged

Document that stack ghci works best only after stack build. #4180

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions doc/ghci.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,3 +75,10 @@ For doing experiments which just involve packages installed in your databases,
it may be useful to run ghci plainly like `stack exec ghci`. This will run a
plain `ghci` in an environment which includes `GHC_PACKAGE_PATH`, and so will
have access to your databases.

*Note*: Running `stack ghci` on a pristine copy of the code doesn't currently
build libraries
([#2790](https://github.com/commercialhaskell/stack/issues/2790)) or internal
libraries ([#4148](https://github.com/commercialhaskell/stack/issues/4148)).
It is recommended to always run a `stack build` before running `stack ghci`,
until these two issues are closed.