- add FAQs for $COMP_CVS_REMOTE and $COMP_CONFIGURE_HINTS

1 files changed, 23 insertions, 1 deletions

diff --git a/README b/README
index cca70a5f..16412522 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-$Id: README,v 1.9 2002/04/03 19:23:42 ianmacd Exp $
+$Id: README,v 1.10 2002/04/03 19:33:20 ianmacd Exp $
 
 
 INSTALLATION
@@ -111,6 +111,28 @@ Q. I author/maintain package X and would like to maintain my own completion
    at the beginning of the main completion script. Any scripts placed in this
    directory will be sourced by interactive bash shells.
 
+Q. I use CVS in combination with passwordless ssh access to my remote
+   repository. How can I have the cvs command complete on remotely checked-out
+   files where relevant?
+
+A. Define $COMP_CVS_REMOTE. Setting this to anything will result in the
+   behaviour you would like.
+
+Q. When I'm running a ./configure script and completion returns a list of
+   long options to me, some of these take a parameter,
+   e.g. --this-option=DESCRIPTION.
+
+   Running ./configure --help lists these descriptions, but everything after
+   the '=' is stripped when returning completions, so I don't know what kind
+   of data is expected as a given option's parameter.
+
+   Is there a way of getting ./configure completion to return the entire
+   option string, so that I can see what kind of data is required and then
+   simply delete the descriptive text and add my own data?
+
+A. Define $COMP_CONFIGURE_HINTS. Setting this to anything will result in the
+   behaviour you would like.
+
 Q. This code is rubbish/not bad/pretty good/the best thing since sliced bread.
    How can I show my appreciation?