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
When I run dune build, it's pretty clear what the current errors are. The [terminal prompt] dune build line is a pretty clear separator.
Lately, I've been using dune build -w, which has a smoother integration with VSCode, and makes me do less overall. Unfortunately, this makes it difficult to see where the current error report starts, and old error reports end. I think readability would greatly improve if we printed a header at the beginning of each error report outputted by dune build -w. This could be something as detailed as
Build failed with X errors:`
(hopefully with nice colors), or as simple as a line of = or - signs.
Note that this also applies to the first error report, as dune build -w seems to clear the terminal line that invoked it.
The text was updated successfully, but these errors were encountered:
When I run
dune build
, it's pretty clear what the current errors are. The[terminal prompt] dune build
line is a pretty clear separator.Lately, I've been using
dune build -w
, which has a smoother integration with VSCode, and makes me do less overall. Unfortunately, this makes it difficult to see where the current error report starts, and old error reports end. I think readability would greatly improve if we printed a header at the beginning of each error report outputted bydune build -w
. This could be something as detailed as(hopefully with nice colors), or as simple as a line of
=
or-
signs.Note that this also applies to the first error report, as
dune build -w
seems to clear the terminal line that invoked it.The text was updated successfully, but these errors were encountered: