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
This seems like a long-standing issue in multiple cabal commands. Perhaps we should take inspiration from other project build tools and try to come up with a fix once and for all? E.g., cargo seems to printing everything to stderr (rustc errors, progress notifications, etc...).
A disadvantage of sending all output to stderr is that we probably break someone's scripts.
Describe the bug
cabal list-bin
doesn't suppress stdout from internal cabal phases, leading to broken behavior when you want to save the result in a variable.To Reproduce
git clone [email protected]:hasufell/list-bin.git
cd list-bin
cabal build
foo=$(cabal list-bin exe:list-bin)
${foo}
Resulting in:
Expected behavior
The only thing sent to stdout is the binary location.
System information
cabal
: 3.10.3.0The text was updated successfully, but these errors were encountered: