From: Paul Eggert <eggert@cs.ucla.edu>
Date: Fri, 8 Mar 2013 17:22:48 +0000 (-0800)
Subject: doc: explain why single-quoting is better
X-Git-Tag: v2.69b~157
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=845e703afd505f1f5ca7649fc1730258573e0f3a;p=thirdparty%2Fautoconf.git

doc: explain why single-quoting is better

* doc/autoconf.texi (Build Directories): Explain single-quoting.
Reported by Markus Elfring in
<http://savannah.gnu.org/support/?108262>.
---

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index bf4823d57..c54c5b351 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -3148,7 +3148,10 @@ versions of @command{make} do not set @code{$<} in explicit rules; they
 expand it to an empty value.
 
 Instead, Make command lines should always refer to source
-files by prefixing them with @samp{$(srcdir)/}.  For example:
+files by prefixing them with @samp{$(srcdir)/}.  It's safer
+to quote the source directory name, in case it contains characters that
+are special to the shell.  Because @samp{$(srcdir)} is expanded by Make,
+single-quoting works and is safer than double-quoting.  For example:
 
 @example
 time.info: time.texinfo