From 1505cc3d8114a0b78617b26cfe2bd0fc6fbfeaaa Mon Sep 17 00:00:00 2001
From: axel <axel@liljencrantz.se>
Date: Sat, 28 Jan 2006 12:19:33 +1000
Subject: [PATCH] Add comment in documentation for set builtin about not
 allowing switches after non-switches

darcs-hash:20060128021933-ac50b-db340075e9a57b41a91d6b64d56d9b5579185254.gz
---
 doc_src/set.txt | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/doc_src/set.txt b/doc_src/set.txt
index b994cd02e..eda46da9c 100644
--- a/doc_src/set.txt
+++ b/doc_src/set.txt
@@ -27,8 +27,14 @@ If a variable is set to more than one value, the variable will be an
 array with the specified elements. If a variable is set to zero
 elements, it will become an array with zero elements.
 
-If the variable name is one or more array elements, such as <code>PATH[1
-3 7]</code>, only those array elements specified will be changed.
+If the variable name is one or more array elements, such as
+<code>PATH[1 3 7]</code>, only those array elements specified will be
+changed.
+
+The set command requires all switch arguments to come before any
+non-switch arguments. For example, <code>set flags -l</code> will have
+the effect of setting the value of the variable <code>flags</code> to
+'-l', not making the variable local.
 
 \subsection set-example Example