- remove section on colons making completion go awry

BUGS

@@ -1,4 +1,4 @@
-$Id: BUGS,v 1.1 2002/07/23 16:02:26 ianmacd Exp $
+$Id: BUGS,v 1.2 2002/10/05 09:55:09 ianmacd Exp $
 
 The following are known bugs with the bash completion code. See also the
 KNOWN PROBLEMS section of the README file.
@@ -20,29 +20,3 @@ KNOWN PROBLEMS section of the README file.
   The answer would seem to be to pass the arguments to mv without performing
   expansion, but this is very tricky to get right and I have been unable to
   devise a reliable way of doing it thus far.
-
-- colons make completion go awry
-
-  bash gives special treatment to a colon in command lines. Although this
-  is not documented, a colon basically starts a new completion token. This
-  is often useful behaviour, as it allows a completion to work in a command
-  like the following:
-
-  $ export PATH=/bin:/sbin:/usr:/usr/<Tab>
-
-  If bash did not treat the colon (and, incidentally, the '=') as special,
-  bash would try to complete on the single token '/bin:/sbin:/usr:/usr/'.
-
-  However, this behaviour is less desirable when performing a command such
-  as this:
-
-  $ scp foo.txt user@machine:<Tab>
-
-  Here, scp is receiving two arguments, but the presence of the colon
-  confuses the completion function into thinking that it needs to perform
-  completion for the last token from scratch, so you end up with nonsensical
-  completions.
-
-  The special treatment of the colon cannot be turned off in bash, so the
-  only way to work around this problem is to escape the colon with a
-  backslash when you want it to be treated as a normal character.