formatter

Prettier 2.4.1
[Playground link](https://prettier.io/playground/#N4Igxg9gdgLgprEAuEAdKABAZhATgdwENcATAAgHIcIA6AZzDrorPwEsYALMgCnTLIASSAFsADtAQw6SMrjgkANOgCUAbnQhFICGJhtodZKGK4I+AArEERlIQA2RAJ5HtAI1yEwAazgwAyoQicAAybFBwyFgOdHDunj5+-mJe4QDmyDC4AK5xIHAibgokCiGEUGnZhGlwAGJ4IoQw+hXIIITZMBBaIJwwIvYA6pwccHQpYHD+NhxsAG4cTm2MriDhsbgwFp5pjVExeQBWdAAe-un2cACK2RDw+-ax2im4G20MTD1iuOEwg2wkLjIAAcAAZnmZYoNPG

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

I'm struggling to understand what's wrong with this sample:

$ shfmt
@() {
    echo "$@"
}
@ hello world\!
<standard input>:3:1: "}" can only be used to close a block

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.