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
I use bat whenever I need better syntax highlighting in my output. E.g. pkl eval foo.pkl | bat -l yaml.
The --format flag can be ignored by a Pkl program by setting it directly in the module, so it's not really clear how we can add proper syntax highlighting here.
It'd be good to colorize the output in case of errors, though.
Might be doable to have the renderers themselves add ANSI escape sequences.
Would need to somehow know whether the CLI command is being run in interactive mode or not.
Generally CLI commands should strip colors if run in a non-interactive context (e.g. pkl eval foo.pkl > output.yaml should not include ANSI escape codes). And it's common to have a --color flag that overrides the default behavior (e.g. --color=always to keep color regardless of interactive mode).
I was watching Viktor's review of pkl and the lack of syntax highlighting shouted me when running
pkl eval
on the command line.I'm so used to color based syntax highlighting in all languages it really shouts to me when there's no color
I wonder if we should have an optional colour option to
pkl eval
that could use ANSI colours to make the output look nicer?The text was updated successfully, but these errors were encountered: