At least for the app/dev/debug part I agree with you. Especially for newcomers this part might not be really clear.

@xabbuh any thoughts?

Im just playing around with it.. not sure if this is it though. Some things i like (kernel@env format, better signal colors), some things i dont (colors 😅, brackets i guess =/)

edit:

Trick/ugly part is the debug thingy imo, but i kinda like this till that.

In my opinion the latest proposal is more confusing than the existing line.

We could go for the explicit way:

Symfony 3.2.0-DEV (kernel: app) (env: dev) (debug: true)

Makes sense =/ :+1: for removing "version"

What about colors?

edit:

Maybe use on/off for debug?

I think debug: false shouldn't be red, red means an error and disabling debug is a totally valid thing.

I know.. therefore i proposed on/off instead of true/false. Imho red/green also signals on/off. But maybe keeping it simple is a good thing, ie plain text except for the version.

edit:
Do we want UTF8 chars? I.e. we could als play with ✓ & ✗

Do we want UTF8 chars? I.e. we could als play with ✓ & ✗

This is not supported by Windows terminals.

What if we don't use color at all?

If not possible, please don't try to convey the information with colors. Color blindness, specially for green/red, is very common for humans: ~8% of males suffer it (but only 0.5% of females) see reference

Globally? The whole console is pretty colorful right now and can be controlled by --[no-]ansi anyway.

Or do you propose
Symfony 3.2.0-DEV (kernel: app) (env: dev) (debug: true) literally?

If not possible, please don't try to convey the information with colors.

You mean "If possible" right?

I you really want to use colours here, I would use them to distinguish keys and values, but I would not use a colour that is dependent on the actual value.

Agreed with @xabbuh since using colors this way can make parentheses needless

Imo we need some form of separation..

• separating metadata from the version (e.g. v3 with parentheses)
• separating key/value pairs (e.g. v3 with comma)

My preference would be the third option.

Mine too :)

Btw, would it make sense to let it interact with output verbosity? I.e. bin/console -V vs. bin/console -V --verbose