X-Git-Url: https://git.madduck.net/etc/vim.git/blobdiff_plain/658eb7161d8d0c23bafe4881e70518c33a74a4c1..e9a940d69e789ce8caf1f3c1ded786dc102df2fd:/README.md

diff --git a/README.md b/README.md
index af1f847..8212e42 100644
--- a/README.md
+++ b/README.md
@@ -80,6 +80,13 @@ Options:
   -q, --quiet                 Don't emit non-error messages to stderr. Errors
                               are still emitted, silence those with
                               2>/dev/null.
+   --pyi                      Consider all input files typing stubs regardless
+                              of file extension (useful when piping source on
+                              standard input).
+  --py36                      Allow using Python 3.6-only syntax on all input
+                              files.  This will put trailing commas in function
+                              signatures and calls also after *args and
+                              **kwargs.  [default: per-file auto-detection]
   --version                   Show the version and exit.
   --help                      Show this message and exit.
 ```
@@ -380,7 +387,7 @@ decision = (maybe.this() and values > 0) or (maybe.that() and values < 0)
 
 Some popular APIs, like ORMs, use call chaining.  This API style is known
 as a [fluent interface](https://en.wikipedia.org/wiki/Fluent_interface).
-*Black* formats those treating dots that follow a call or an indexing
+*Black* formats those by treating dots that follow a call or an indexing
 operation like a very low priority delimiter.  It's easier to show the
 behavior than to explain it.  Look at the example:
 ```py3
@@ -653,6 +660,10 @@ More details can be found in [CONTRIBUTING](CONTRIBUTING.md).
 
 ### 18.5b1 (unreleased)
 
+* added `--pyi` (#249)
+
+* added `--py36` (#249)
+
 * Python grammar pickle caches are stored with the formatting caches, making
   *Black* work in environments where site-packages is not user-writable (#192)
 
@@ -666,7 +677,8 @@ More details can be found in [CONTRIBUTING](CONTRIBUTING.md).
 
 * fixed unstable formatting when inline comments were moved around in
   a trailer that was omitted from line splitting on a large expression
-  (#238) 
+  (#238)
+
 
 ### 18.5b0