Closed m4lvin closed 3 months ago
@m4lvin, thanks for the suggestion. I'll try to implement it.
This is implemented in Stack's master
branch. If you are not using GHCup to manage versions of Stack: stack upgrade --source-only --git
.
Wow, super quick!
Looking at the code and because I just now saw the notification about nix
being in my PATH the first time, maybe a generic way to set notifyIfNixOnPath
, notifyIfGhcUntested
and so on with stack config
would make sense?
@m4lvin, I am happy to add those too. My general approach to extending stack config set
is a conservative one: to do it only on the basis of an identified genuine user need.
Okay, I do not actually have a specific need for that one.
I was expecting
to work, similar to
stack config set system-ghc --global true
etc.This would provide a more programmatic way to disable the warning shown when running an old version of stack:
(Motivation/background: I am running
stack
in containers for autograding student code. They should not see with this warning (and in other steps I use--silent
, but here I want to show compile errors). For now I have a script to write toconfig.yml
manually, but that seems a bit fragile.)