Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3B391C50.96B6FE0D@ece.gatech.edu> Date: Tue, 26 Jun 2001 19:35:44 -0400 From: Charles Wilson X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: tiberius AT braemarinc DOT com CC: "Cygwin Mailing List (E-mail)" Subject: Re: Tab completion broken in latest Cygwin snapshots References: <000501c0fe78$3cf95e00$1101a8c0 AT BRAEMARINC DOT COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Gary R. Van Sickle" wrote: > > BASH tab completion hasn't worked on shell scripts in the snapshots since > cygwin1.dll went from ~700KB to ~900kb (what was the major addition?). > E.g., try to tab-complete the './configure' script of your favorite > package - it doesn't work. Exe's tab-complete fine. cygcheck below. bash is smart. If the tab-completion is for the first "word" on a line, then bash assumes that you want an executable file -- so only those files marked executable (according to ls -l) are candidates for completion. (.exe files are a special case and are always considered executable). Is your ./configure script marked +x ? If the tab-completion is for anything other than the first "word" on a line, then bash assumes you are looking for any file to be used as the argument for the command specified by the first word. Try this: $ foo conf and you should see $ foo configure regardless of whether configure is marked +x. --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/