Mail Archives: cygwin/2005/01/17/14:31:18
Igor Pechtchanski schrieb:
> On Mon, 17 Jan 2005, Christopher Faylor wrote:
>>On Sun, Jan 16, 2005 at 08:43:44PM -0500, Pierre A. Humblet wrote:
>>>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:~".
>>
>>Great point. Thanks, Pierre.
>>Should this be a default in a .profile (or equivalent) somewhere?
>
> Unfortunately, this isn't necessarily good to have as a default setting,
> since putting .dll in $FIGNORE will disable completion in all cases, not
> just when searching for an executable. In other words, if you have a file
> foo.dll, and try to get gcc to link with it while having .dll in $FIGNORE,
> typing in "gcc blah.c foo<TAB>" will not produce a match with foo.dll
> (same with "cp", etc). If there were a way to restrict .dll completion
> *only* for cases when an executable is needed, that would be a good
> candidate for a default setting.
I'll look to add this to my bash_completion package.
http://xarch.tu-graz.ac.at/publ/cygwin/release/bash_completion/
--
Reini Urban
--
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/
- Raw text -