Message-Id: <20101102205025.150395100@gmail.com>
User-Agent: quilt/0.48-1
Date: Tue, 02 Nov 2010 13:49:00 -0700
From: dan DOT colascione AT gmail DOT com
To: cygwin AT cygwin DOT com
Subject: [patch 5/8] Document completion_strip_exe in Cygwin readme
References: <20101102204855 DOT 153395100 AT gmail DOT com>
Content-Disposition: inline; filename=completion-exe-cygwin-doc
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Index: bash-3.2/CYGWIN-PATCHES/bash.README
===================================================================
--- bash-3.2.orig/CYGWIN-PATCHES/bash.README
+++ bash-3.2/CYGWIN-PATCHES/bash.README
@@ -62,7 +62,15 @@ of completion and PATH searching. The `t
 are not affected. Use this variable to prevent non-executables
 uselessly appearing in completion lists; EXECIGNORE=*.dll is quite
 useful.
-9. If you don't like how bash behaves, then propose a patch, rather than
+9. This version of bash has a Cygwin-specific shell option
+completion_strip_exe. It is enabled by default. With this option on,
+whenever bash sees a file "foo.exe" when trying to complete a command
+name, it checks whether Cygwin has generated a pseudo-hardlinked "foo"
+short name for the file and uses that instead. The end result is that
+the names of native Windows programs are completed normally, resulting
+in a more Unix-like experience overall. This substitution does not
+occur if "foo.exe" and "foo" are, in fact, different files.
+10. If you don't like how bash behaves, then propose a patch, rather than
 proposing idle ideas.  This turn of events has already been talked to
 death on the mailing lists by people with many ideas, but few patches.
 

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple