Add support for rendering console output with colors

[lafriks]

Fixes #19392

Extension .sh-session would be automatically rendered as console output

Screenshot:

[wxiaoguang]

I am very curious why the colored logs should be submitted into a git repository .... it violates the git usage.

If someone really needs to use git to manage their logs, they can use an external render IMO.

[lafriks]

It's not only about logs, it's also about console output from many tools. Git can be used not only for code but also for documentation, it's quite common to store tool report output when doing either software functionality, load/stress or security testing and many tools does colored output for it's reports that in git become quite unreadable, thus this PR :)

[Gusted]

It's unfortunate that the package doesn't support io.Reader, but code-wise LGTM.

[silverwind]

Do I understand correctly that it would render any file that contains a literal \x1b as console output, even if the file may be a regular source code file? If yes, maybe we should skip rendering as console output if enry detects something else.

Also note that inside markdown ```console or ```bash snippets are pretty common, maybe we could also render them colored, but I would not change the background color to black of such snippets.

[lafriks]

Do I understand correctly that it would render any file that contains a literal \x1b as console output, even if the file may be a regular source code file? If yes, maybe we should skip rendering as console output if enry detects something else.

True, I have added enry check and only if enry does not detect it as anything (detects as lang other) than it's rendered as console output.

Also note that inside markdown ```console or ```bash snippets are pretty common, maybe we could also render them colored

bash snippet should not be rendered as console output as that bash or sh usually means script code not console output. Only console could be rendered but that is not currently possible by markdown rendering library. At least I could not find how to implement it.

but I would not change the background color to black of such snippets.

Their background color would have to be changed as color codes in console output are usually meant to be displayed on black background thus there is high chance that part of that could be unreadable because of that.

[silverwind]

Only console could be rendered but that is not currently possible by markdown rendering library. At least I could not find how to implement it.

No big issue, maybe it's something for later.

Their background color would have to be changed as color codes in console output are usually meant to be displayed on black background thus there is high chance that part of that could be unreadable because of that.

Ideally the console should also have a light background on light theme. It'd certainly possible to ensure contrast via different colors for light/dark. But I guess if you're happy with just one theme, we can go with that now.

[lafriks]

One theme should be ok for now as usually terminal windows still have black background even on light themed desktop environment

[lunny]

How about allow users setting extensions but not have the detection because the detection maybe wrong?

[lafriks]

It will try to detect only after language detection is done and would be otherwise rendered as plain text so chance of false rate is low. Also you can always switch to plain text display