From: David W.H. Swenson Date: Sun, 18 Oct 2020 21:27:15 +0000 (+0200) Subject: Fix GitHub markdown links to work on RTD (#1752) X-Git-Url: https://git.madduck.net/etc/vim.git/commitdiff_plain/3e3da8eef6f4ba48da1505ad68ca0e1d788f6d6b Fix GitHub markdown links to work on RTD (#1752) * Fix internal links to work on RTD Note that these still lead to GitHub, instead of staying on RTD. * Point links to better anchors --- diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d446e6a..a4250f7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -52,7 +52,7 @@ your PR. You may need to change configuration for it to pass. For more `black-primer` information visit the -[documentation](https://github.com/psf/black/blob/master/docs/black_primer.md). +[documentation](https://github.com/psf/black/blob/master/docs/black_primer.md#black-primer). ## Hygiene diff --git a/README.md b/README.md index 7cd4d7f..4747281 100644 --- a/README.md +++ b/README.md @@ -164,7 +164,7 @@ about _Black_'s changes or will overwrite _Black_'s changes. A good example of t should be configured to neither warn about nor overwrite _Black_'s changes. Actual details on _Black_ compatible configurations for various tools can be found in -[compatible_configs](https://github.com/psf/black/blob/master/docs/compatible_configs.md). +[compatible_configs](https://github.com/psf/black/blob/master/docs/compatible_configs.md#black-compatible-configurations). ### Migrating your code style without ruining git blame diff --git a/docs/authors.md b/docs/authors.md index ebf64ea..cdf5046 100644 --- a/docs/authors.md +++ b/docs/authors.md @@ -133,6 +133,7 @@ Multiple contributions by: - [Paul Ganssle](mailto:p.ganssle@gmail.com) - [Paul Meinhardt](mailto:mnhrdt@gmail.com) - [Peter Bengtsson](mailto:mail@peterbe.com) +- [Peter Grayson](mailto:pete@jpgrayson.net) - [Peter Stensmyr](mailto:peter.stensmyr@gmail.com) - pmacosta - [Quentin Pradet](mailto:quentin@pradet.me) diff --git a/docs/change_log.md b/docs/change_log.md index e183ca5..1ee35a4 100644 --- a/docs/change_log.md +++ b/docs/change_log.md @@ -17,6 +17,12 @@ - fixed a crash when PWD=/ on POSIX (#1631) +- fixed "I/O operation on closed file" when using --diff (#1664) + +- Prevent coloured diff output being interleaved with multiple files (#1673) + +- Added support for PEP 614 relaxed decorator syntax on python 3.9 (#1711) + ### 20.8b1 #### _Packaging_ diff --git a/docs/contributing_to_black.md b/docs/contributing_to_black.md index 8e33299..f0be872 100644 --- a/docs/contributing_to_black.md +++ b/docs/contributing_to_black.md @@ -54,7 +54,7 @@ your PR. You may need to change configuration for it to pass. For more `black-primer` information visit the -[documentation](https://github.com/psf/black/blob/master/docs/black_primer.md). +[documentation](https://github.com/psf/black/blob/master/docs/black_primer.md#). ## Hygiene diff --git a/docs/installation_and_usage.md b/docs/installation_and_usage.md index 7de8b65..c91a1c4 100644 --- a/docs/installation_and_usage.md +++ b/docs/installation_and_usage.md @@ -119,7 +119,7 @@ about _Black_'s changes or will overwrite _Black_'s changes. A good example of t should be configured to neither warn about nor overwrite _Black_'s changes. Actual details on _Black_ compatible configurations for various tools can be found in -[compatible_configs](https://github.com/psf/black/blob/master/docs/compatible_configs.md). +[compatible_configs](https://github.com/psf/black/blob/master/docs/compatible_configs.md#). ## Migrating your code style without ruining git blame @@ -167,12 +167,13 @@ know!) ## NOTE: This is a beta product -_Black_ is already [successfully used](#used-by) by many projects, small and big. It -also sports a decent test suite. However, it is still very new. Things will probably be -wonky for a while. This is made explicit by the "Beta" trove classifier, as well as by -the "b" in the version number. What this means for you is that **until the formatter -becomes stable, you should expect some formatting to change in the future**. That being -said, no drastic stylistic changes are planned, mostly responses to bug reports. +_Black_ is already [successfully used](https://github.com/psf/black#used-by) by many +projects, small and big. It also sports a decent test suite. However, it is still very +new. Things will probably be wonky for a while. This is made explicit by the "Beta" +trove classifier, as well as by the "b" in the version number. What this means for you +is that **until the formatter becomes stable, you should expect some formatting to +change in the future**. That being said, no drastic stylistic changes are planned, +mostly responses to bug reports. Also, as a temporary safety measure, _Black_ will check that the reformatted code still produces a valid AST that is equivalent to the original. This slows it down. If you're