You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
install the backend with stack (stack install hyper hyper-haskell-server) - global resolver is lts-11.15, and stack is in ~/.local/bin/
open frontend; set interpreter back-end to stack; set location of stack executable in preferences
reload imports
Result:
Status: Could not load imports:
Interpreter not running (Error: 1)
Related observations:
If the stack path is set to the folder containing stack (rather than the full path) the error message is unhelpful:
It's not clear when changes to the stack path preference are actually applied; I could change which error I got by changing the interpreter back-end to cabal, reloading, and then changing back to stack.
The text was updated successfully, but these errors were encountered:
env['PATH'] = process.env['PATH'] + ':/usr/local/bin' // pick up path from external environment if possible
My reasoning was that this path is standard enough and it doesn't hurt to include it.
In your case, this trick doesn't work, because your stack binary is not in a standard location. A temporary fix would be simply add your nonstandard path by hand. You can mess around with the HyperHaskell.app bundle if you like, I think the JavaScript source code is included.
The proper fix would be to extract the path from the preferences
You make a good point that it's not clear when the preferences are applied.
I have stack in ~/.local/bin/ too. I think it's pretty standard, so it wouldn't hurt to hardcode it in as well. Is it not possible to call which stack from within JS? Wouldn't process.env['PATH'] pick it up anyway, since the fact that stack is called means that it already is in the user's PATH?
Edit: stack is actually weird, in that it copies itself to both ~/.local/bin/ and /usr/local/bin/ in some (or all?) cases.
Steps to reproduce:
stack install hyper hyper-haskell-server
) - global resolver is lts-11.15, and stack is in ~/.local/bin/Result:
Related observations:
If the stack path is set to the folder containing stack (rather than the full path) the error message is unhelpful:
It's not clear when changes to the stack path preference are actually applied; I could change which error I got by changing the interpreter back-end to cabal, reloading, and then changing back to stack.
The text was updated successfully, but these errors were encountered: