Closed freeman42x closed 6 years ago
Ehehe. Making libraries visible to the plugin will almost certainly break stuff. I would suggest adding
-ignore-dot-ghci
to extraArgs
setting:
Thank you very much. That worked!
@lierdakil Unfortunately this disables using any .ghci file including the one in a project root. I'm looking into what arguments need to be passed to GHCI for it to load those libraries it requires.
Adding the global .ghci library dependency to the cabal file fixed the warnings (but not really a solution):
build-depends:
base >=4.7 && <5,
time,
ipprint,
hscolour
I also tried to tell ghci
to load the packages using Extra Args with -package ipprint
but that completely crashed the REPL without any error message - the text box for issuing commands dissapeared.
But then it still errord with:
Not in scope: ‘myPrint’
And 2 warnings:
Some flags have not been recognized: prompt-cont, |
Some flags have not been recognized: prompt-cont,
First one is caused by :set prompt-cont " | "
from global .ghci
, the other warning comes from ide-haskell-repl, related issue: https://github.com/atom-haskell/ide-haskell-repl/issues/58
Long story short: use stack repl
or cabal repl
with an appropriately configured Stack/Cabal project to bring libraries into repl scope.
This package can not support arbitrary .ghci
configs. If you want that, consider just running ghci from a terminal (embedded into Atom or not, see f.ex. terminal-plus or atom-domterm packages).
If you still want to make it work somehow, you're on your own.
When the plugin loads it prints in the IDE-Haskell error tab:
These happens because in
~/.ghci
I have added a custom pretty printer to get colored output in ghci when it is run from a usual terminal:.ghci
.ghci.hs
Any suggestion of how to make the libraries visible to the plugin (preferably in a global way)?