doc: clarify that CLI invocation must always be valid

This comes up as a corner case where folks provide -e/--regexp in a
configuration file and then expect to be able to run 'rg' with no args.
However, ripgrep fails because it still expects at least one pattern
even though one was specified in the config file.

This occurs because ripgrep has to parse its CLI parameters before
reading the config file. (For log output settings and to handle the
--no-config flag.) This initial parse will fail if there are no patterns
specified.

The only way to solve this that I can see is to somehow relax the
requirements of the initial parse. But this is problematic because we
would still need to enforce those requirements in cases where we don't
do a second parse (when no config file is present).

All in all, this doesn't seem like a problem that is worth solving.

Closes #1730

doc/rg.1.txt.tpl

@@ -191,10 +191,12 @@ simple. It is defined by two rules:
        whitespace) are ignored.
 
 ripgrep will look for a single configuration file if and only if the
-*RIPGREP_CONFIG_PATH* environment variable is set and is non-empty.
-ripgrep will parse shell arguments from this file on startup and will
-behave as if the arguments in this file were prepended to any explicit
-arguments given to ripgrep on the command line.
+*RIPGREP_CONFIG_PATH* environment variable is set and is non-empty. ripgrep
+will parse shell arguments from this file on startup and will behave as if
+the arguments in this file were prepended to any explicit arguments given to
+ripgrep on the command line. Note though that the 'rg' command you run must
+still be valid. That is, it must always contain at least one pattern at the
+command line, even if the configuration file uses the '-e/--regexp' flag.
 
 For example, if your ripgreprc file contained a single line: