Skip to content
This repository has been archived by the owner on Jun 4, 2024. It is now read-only.

Better Zinc Log Format #200

Open
borkaehw opened this issue Jul 23, 2019 · 6 comments
Open

Better Zinc Log Format #200

borkaehw opened this issue Jul 23, 2019 · 6 comments

Comments

@borkaehw
Copy link
Collaborator

The Zinc output log is getting harder to read whenever we get a lot of messages, especially with long file path and long messages.
Screenshot from 2019-07-23 16-15-32

It would be good if we can come out with an idea of improving the readability. Adding distinction to the file path would be one option, it becomes more clear where the actually message starts.

How about making it bold?
Screenshot from 2019-07-23 16-14-20

How about putting new lines?
Screenshot from 2019-07-23 16-16-58

Or we could have both?
Screenshot from 2019-07-23 16-17-44

Any suggestion will be appreciated. Thanks.

@borkaehw
Copy link
Collaborator Author

@SrodriguezO @sriraamas @jjudd @andyscott What do you think?

@SrodriguezO
Copy link
Collaborator

I like the idea of adding newlines between errors. I'm also open to making the file path bold, but the biggest gains in readability seem to be the newlines.

@sriraamas
Copy link

sriraamas commented Jul 23, 2019

a colon(:) after the line number can also make things a little better. Am not sure about underline, but I think the newline, does run the risk of not-so-compact output, while improving readability.

@sriraamas
Copy link

May be it will make sense to also have `[Error] on the blank newline, so that it doesn't seem too chopped up.

@SrodriguezO
Copy link
Collaborator

I thought underline would be a good idea too, but it makes the output look like a bunch of links

@pauldraper
Copy link
Contributor

Paths would be shorter without src/main/scala pasted everywhere :/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants