This is the mail archive of the
cygwin
mailing list for the Cygwin project.
[patch 2/8] Document EXECIGNORE in Cygwin readme
- From: dan dot colascione at gmail dot com
- To: cygwin at cygwin dot com
- Date: Tue, 02 Nov 2010 13:48:57 -0700
- Subject: [patch 2/8] Document EXECIGNORE in Cygwin readme
- References: <20101102204855.153395100@gmail.com>
Index: bash-3.2/CYGWIN-PATCHES/bash.README
===================================================================
--- bash-3.2.orig/CYGWIN-PATCHES/bash.README
+++ bash-3.2/CYGWIN-PATCHES/bash.README
@@ -55,7 +55,14 @@ is on a binary mount with igncr disabled
would be text mounts with igncr disabled and no \r in the underlying file.
Next would be binary mounts with igncr enabled. And the slowest that bash
will operate is on text mounts with igncr enabled.
-8. If you don't like how bash behaves, then propose a patch, rather than
+8. This version of bash has a new special variable EXECIGNORE. It is a
+colon-separated list of extended glob patterns. If a file's full path
+matches one of these, it is no considered executable for the purposes
+of completion and PATH searching. The `test', `[', and `[[' builtins
+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
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