Always show both stdout and stderr for code blocks

[mmlb]

Changes Introduced

• Always display stdout from code blocks (even if an error occurs) as it may be relevant
• Display stderr from code blocks as it may be relevant too

[mmlb]

Gentle ping to @maaslalani

[maaslalani]

Thanks @mmlb!

[maaslalani]

@mmlb I'm not a huge fan of the error messages produce by the stderr because of the tmp file. I wonder if there's a better solution (perhaps a different keybinding, to also receive the stderr)?

Alternatively, I wonder if we can scrub the file name from the Output which would solve the issue.

[mmlb]

Yeah agree about that. I would not like to have a different key binding, I can take a look at dropping the filename.

[mmlb]

@maaslalani I've pushed a quick hack to get rid of the name (only tested on go and bash atm) how's this error output look?

I'm not a fan of the # command-line-arguments and some of the other stuff but I don't think it should be removed, if the $tool adds it then it should be there I think.

[tploss]

Gentle ping, @maaslalani and @mmlb
Any update on this PR?

[mmlb]

Looking for any feedback

[maaslalani]

Hey @mmlb, I don't like the idea of the OutputReplacement since it makes adding a language have more friction. I'm not sure the correct approach but I think my thinking would be a separate key bind / extra step to reveal the full error so that it doesn't cloud up the presentation by accident during a live presentation.

[maaslalani]

Another option is to log to a temporary file which people can inspect?