Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <4143D122.B7BA2D15@dessent.net> Date: Sat, 11 Sep 2004 21:31:30 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: What is executable or not...? References: <41439D4D.1050001@tlinx.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com linda w wrote: > When I am in bash, I can type a completion char for my executable and it > will > give me a list of all the executables that could complete my command. > > The command completion doesn't give a complete listing of all files, but > oddly, > it does include many ".dll's", most that would seem to be > non-executable...like: Because to bash any file with the 'x' bit set is an executable. This is how it works in *nix / posix and that's what Cygwin is emulating. I think if you were to "chmod a-x" your DLLs you'd run into serious problems so I suggest you not do that. You should read the bash manual section 8.6: You could probably change the completion behavior so that "*.[dD][lL][lL]" doesn't match, if it really bothers you. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/