formatter

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

% gosh
$ date ; time sleep 31 ; date
Tue Nov 30 12:12:05 EST 2021

real	0m-28.990s
user	0m0.000s
sys	0m0.000s
Tue Nov 30 12:12:36 EST 2021

Implementation of time uses math.Remainder, which can return negative numbers for two positive arguments.

https://github.com/mvdan/sh/blob/23a22509643c2fa771e7b722c784707c1d3b4b2f/interp/runner.go#L712

See [this](https://go.dev/p

Good evening!
This is a feature request (AFAIKT there's no configuration option or duplicate issue for this).

In many cases where nightly rustfmt is applied by CI in public repositories, users will often run cargo fmt themselves directly or through their editor causing warnings arising from using the stable rustfmt where the nightly is required. E.g.:

$ cargo fmt
Warning

This plugin is not GDPR-compliant and the same might be true for other privacy regulations, e.g. the CCPA. I will continue to use the GDPR as an umbrella term for similar regulations.

At the time of this writing, the authors assume that consent is given through the co

We need to update our README.md file before the 1.0 release.