Update clang-tidy documentation.

[alexfh]

Summary

Updated the help message, updated description of -checks=, removed
mentions of -disable-checks.

[alexfh]

Added information about -checks='*' to -list-checks help message. Reformatted
option descriptions, so that they fit into 80 columns on the terminal.

[klimek]

lg

clang-tidy/tool/ClangTidyMain.cpp

38 ↗

(On Diff #9457)

I think this needs some more explanation of how you decide whether something is positive or negative, whether order is important, how it relates to the default checks, etc.

[alexfh]

Please take a look if the new description is more clear.

[klimek]

lg

docs/clang-tidy.rst

 compilation options on the command line after ``--``:
 
 .. code-block:: bash
 
   $ clang-tidy test.cpp -- -Imy_project/include -DMY_DEFINES ...
 
 :program:`clang-tidy` has its own checks and can also run Clang static analyzer
 checks. Each check has a name and the checks to run can be chosen using the
-``-checks=`` and ``-disable-checks=`` options. :program:`clang-tidy` selects the
-checks with names matching the regular expression specified by the ``-checks=``
-option and not matching the one specified by the ``-disable-checks=`` option.
+``-checks=`` option, which specifies a comma-separated list of positive and
+negative (prefixed with ``-``) globs. Positive globs add subsets of checks,
+negative globs remove them. For example,
 
-The ``-list-checks`` option lists all the enabled checks. It can be used with or
-without ``-checks=`` and/or ``-disable-checks=``.
+.. code-block:: bash
+
+  $ clang-tidy test.cpp -checks='-*,clang-analyzer-*,-clang-analyzer-alpha*'
+
+will disable all default checks (``-*``) and enable all ``clang-analyzer-*``
+checks except for ``clang-analyzer-alpha*`` ones.
+
+The ``-list-checks`` option lists all the enabled checks. When used without
+``-checks=``, it shows checks enabled by default. Use ``-checks='*'`` to see all
+available checks or with any other value of ``-checks=`` to see which checks are
+enabled by this value.
 
 There are currently three groups of checks:
 
 * Checks related to the LLVM coding conventions have names starting with
   ``llvm-``.
 
 * Checks related to the Google coding conventions have names starting with
   ``google-``.
 
+* Checks with names starting with ``misc-`` don't relate to any particular
+  coding style.
+
 * Clang static analyzer checks are named starting with ``clang-analyzer-``.
 
 
 The ``-fix`` flag instructs :program:`clang-format` to fix found errors if
 supported by corresponding checks.
 
 An overview of all the command-line options:
 
General options:
     -help                    - Display available options (-help-hidden
                                for more)
     -help-list               - Display list of available options
                                (-help-list-hidden for more)
     -version                 - Display the version of this program
 
   clang-tidy options:
 
-    -checks=<string>         - Regular expression matching the names of
-                               the checks to be run.
-    -disable-checks=<string> - Regular expression matching the names of
-                               the checks to disable.
+    -analyze-temporary-dtors - Enable temporary destructor-aware analysis
+                               in clang-analyzer- checks.
+    -checks=<string>         - Comma-separated list of positive and
+                               negative globs matching the names of the
+                               checks to be run.
     -fix                     - Fix detected errors if possible.
+    -header-filter=<string>  - Regular expression matching the names of
+                               the headers to output diagnostics from.
+                               Diagnostics from the main file of each
+                               translation unit are always displayed.
     -list-checks             - List all enabled checks and exit.
     -p=<string>              - Build path
 
   -p <build-path> is used to read a compile command database.
 
     For example, it can be a CMake build directory in which a file named
     compile_commands.json exists (use -DCMAKE_EXPORT_COMPILE_COMMANDS=ON
     CMake option to get this output). When no build path is specified,