Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sun, 16 Jan 2005 20:43:44 -0500
From: "Pierre A. Humblet" <pierre.humblet@ieee.org>
To: cygwin@cygwin.com
Subject: Re: Can "DLL's" & libraries be marked as non-executable?
Message-ID: <20050117014343.GA907371@Worldnet>
References: <41E9D722.3010306@tlinx.org> <009001c4fba2$54223c20$e6ec6f83@robinson.cam.ac.uk> <41EAF139.6070102@tlinx.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41EAF139.6070102@tlinx.org>
User-Agent: Mutt/1.4.1i

On Sun, Jan 16, 2005 at 02:56:57PM -0800, linda w wrote:

> I was told I might fix the problem of typing in a partial command name
> like "cyg", and the command completion character and getting a long list
> of DLL's with a few EXE's thrown in.
>
> I had been told it could be fixed through adjustment of the bash command
> completion or in the readline completion used by bash.  This doesn't
> appear to be a straight forward solution.  

Have you looked into it? It's easy in bash:
  FIGNORE
    A colon-separated list of suffixes to  ignore  when  performing
    filename  completion  (see  READLINE  below).  A filename whose
    suffix matches one of the entries in FIGNORE is  excluded  from
    the list of matched filenames.  A sample value is ".o:~".

Pierre

--
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/