formatter

Perhaps we should document this issue in the FAQ? Using pre-commit with Black is pretty common (and it's not always instantly clear it passes all of the files to the hook directly bypassing any file discovery the hook may implement). I'd suggest pre-commit's exclude configurations first, and then black's force-exclude.

_Originally posted by @ichard26 in psf/black#3013

In the second example below, a trailing blank/ white space is inserted after first opening '(' symbol, this is indicated through '^'. The expectation is like in first example above. This seems to happen when opening a subshell first after opening brackets of another subshell.
shfmt is called without any parameters in this case.

#!/bin/bash

# OK - no blank
(
    cd .
    (echo "Hello

The motivation for this new option is outlined in #5345, and the option proposed here is a potential solution to that scenario.

Specifically, we need to introduce a new config option named something like doc_comment_code_block_width (but feel free to come up with a better name) that's used to set the width threshold used when rustfmt is reformating code blocks residing within doc comments.

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.