code

Describe the bug

"EOF in multi-line statement" error is shown to the user as the raw tuple it was returned as, rather than in a nicely formatted message.

To Reproduce

For example:

1. Take this (invalid) file:

print(

2. Run Black on it with no arguments
3. See a message with the EOF error being shown as a raw tuple representation:

error: cannot format test

Related with nunomaduro/phpinsights#23 will be a great idea to allow set all commands parameters from config/insights.php when is used with php artisan insights.

Maybe something like:

'parameters' => '--format=json -d memo

The fix for #3307 was done for GitRepository only. This bug tracks the rest of the repositories.

Since the default output is meant to be human-readable, would it make sense to add thousands separators to make the output more easily readable?

Lite-xl doesn't remember how i left the zoom level,
I mean when i use it i zoom it a little bit for readability and when i quit and reopen it, that time it doesn't remember how i left it off that is the zoom level.

This is to help people that for whatever reason don't want to go through the effort of changing it manually every time.

Default levels of understanding and thoroughness for both positive (review)and negative(flag) could also be configurable in the user-config file.

Please add C# syntax support.

It would be cool to add Google Translate support, because most likely Google Translate is better than Microsoft Translate.

And maybe it would be good idea to use Google Apps Script, because it has a free unlimited Google Translate. Here is an [example article](https://techstreams.github.io/2016/01/07/translation-automation-with-wor