From 4d5dfbb94e1e1da265c35ba2ebc362e8c8531f41 Mon Sep 17 00:00:00 2001
From: vincentdarley <vincentdarley>
Date: Fri, 24 Aug 2001 16:43:25 +0000
Subject: documented subtlety with glob and windows paths

---
 doc/glob.n | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/doc/glob.n b/doc/glob.n
index 409001b..2ae9df5 100644
--- a/doc/glob.n
+++ b/doc/glob.n
@@ -5,7 +5,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: glob.n,v 1.10 2001/08/23 17:37:07 vincentdarley Exp $
+'\" RCS: @(#) $Id: glob.n,v 1.11 2001/08/24 16:43:25 vincentdarley Exp $
 '\" 
 .so man.macros
 .TH glob n 8.3 Tcl "Tcl Built-In Commands"
@@ -166,6 +166,17 @@ directory of the user whose account information resides on the specified NT
 domain server.  Otherwise, user account information is obtained from
 the local computer.  On Windows 95 and 98, \fBglob\fR accepts patterns
 like ``.../'' and ``..../'' for successively higher up parent directories.
+
+.
+Since the backslash character has a special meaning to the glob 
+command, glob patterns containing Windows style path separators need 
+special care. The pattern \fIC:\e\efoo\e\e*\fR is interepreted as 
+\fIC:\efoo\e*\fR where \fI\ef\fR will match the single character \fIf\fR 
+and \fI\e*\fR will match the single character \fI*\fR and will not be 
+interpreted as a wildcard character. One solution to this problem is 
+to use the Unix style forward slash as a path separator. Windows style 
+paths can be converted to Unix style paths with the command \fBfile
+join $path\fR (or \fBfile normalize $path\fR in Tcl 8.4). 
 .TP 
 \fBMacintosh\fR 
 . 
-- 
cgit v0.12