* auth.texi (Help for users): Explain quoting rules better.

diff --git a/texi/ChangeLog b/texi/ChangeLog
index 7a38f5b..ea17eb1 100644 (file)
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,3 +1,7 @@
+2014-11-02  Teodor Zlatanov  <tzz@lifelogs.com>
+
+       * auth.texi (Help for users): Explain quoting rules better.
+
 2014-10-25  Eric S. Raymond  <esr@thyrsus.com>
 
        * gnus-coding.texi: Neutralized language specific to a repository type.

diff --git a/texi/auth.texi b/texi/auth.texi
index 521358a..94e0871 100644 (file)
--- a/texi/auth.texi
+++ b/texi/auth.texi
@@ -106,12 +106,17 @@ The @code{user} is the user name.  It's known as @var{:user} in
 @code{auth-source-search} queries.  You can also use @code{login} and
 @code{account}.
 
-Spaces are always OK as far as auth-source is concerned (but other
-programs may not like them).  Just put the data in quotes, escaping
-quotes as you'd expect with @samp{\}.
+You can use spaces inside a password or other token by surrounding the
+token with either single or double quotes.
 
-All these are optional.  You could just say (but we don't recommend
-it, we're just showing that it's possible)
+You can use single quotes inside a password or other token by
+surrounding it with double quotes, e.g. @code{"he'llo"}. Similarly you
+can use double quotes inside a password or other token by surrounding
+it with single quotes, e.g. @code{'he"llo'}. You can't mix both (so a
+password or other token can't have both single and double quotes).
+
+All this is optional. You could just say (but we don't recommend it,
+we're just showing that it's possible)
 
 @example
 password @var{mypassword}