Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

usability: print separator between reports with dune build -w #7433

Closed
askvortsov1 opened this issue Mar 28, 2023 · 1 comment
Closed

usability: print separator between reports with dune build -w #7433

askvortsov1 opened this issue Mar 28, 2023 · 1 comment

Comments

@askvortsov1
Copy link

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.

@Alizter
Copy link
Collaborator

Alizter commented Mar 28, 2023

Hi, this was implemented in #6823 and will appear in Dune 3.8. There is a new command line options --display-separate-messages that can be passed.

@Alizter Alizter closed this as completed Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants