- add FAQ on circumventing restricted file name completion of bash completion

by using M-/

README

@@ -1,4 +1,4 @@
-$Id: README,v 1.17 2002/12/17 09:53:18 ianmacd Exp $
+$Id: README,v 1.18 2003/04/21 10:00:03 ianmacd Exp $
 
 
 INSTALLATION
@@ -84,15 +84,13 @@ II.
 The have() function is used to conserve memory by only installing
 completion functions for those programs that are actually present on
 your system. The current method of determining whether or not a given
-binary is present is whether or not it is in your $PATH.
+binary is present is whether or not it can be found along a certain
+path of directories. The path that is currently searched is:
 
-This approach has the disadvantage that sudo completion will not be
-able to perform sub-completion on, say, service, if /sbin is not in
-your path, which, as an unprivileged user, it typically isn't.
+	$PATH:/sbin:/usr/sbin:/usr/local/sbin
 
-The work-around for this is to put all directories of binaries for
-which you require completion into your $PATH variable prior to
-sourcing bash_completion.
+where $PATH is your user path at the time the bash completion file is
+sourced.
 
 III.
 
@@ -104,6 +102,15 @@ may vary.
 FAQ
 ---
 
+Q. The bash completion code inhibits some commands from completing on
+   files with extensions that are legitimate in my environment. Do I
+   have to disable completion for that command in order to complete on
+   the files that I need to?
+
+A. No. Use M-/ to (in the words of the man page) attempt file name
+   completion on the text before the cursor. This will circumvent any
+   file type restrictions put in place by the bash completion code.
+
 Q. How can I insert my own local completions without having to
    reinsert them every time you issue a new release?