This is the mail archive of the
mailing list for the Cygwin project.
Re: No file name completion for file names start with underscore
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Paul.Domaskis <Paul dot Domaskis at gmail dot com>, cygwin at cygwin dot com
- Date: Sat, 20 Sep 2014 08:27:34 +0400
- Subject: Re: No file name completion for file names start with underscore
- Authentication-results: sourceware.org; auth=none
- References: <loom dot 20140918T010225-301 at post dot gmane dot org> <loom dot 20140918T011028-898 at post dot gmane dot org> <loom dot 20140918T012259-677 at post dot gmane dot org> <20140918000242 dot GA17489 at phoenix> <CACUHbYP+hmbvkVK_dO_C6H3QMLO3zGH+sK2fSovHox3XLUsWUQ at mail dot gmail dot com> <lvf9re$l0j$1 at ger dot gmane dot org> <loom dot 20140918T223627-193 at post dot gmane dot org> <20140918221943 dot GA22077 at phoenix> <loom dot 20140919T233113-212 at post dot gmane dot org>
- Reply-to: cygwin at cygwin dot com
>> David is right: find does accept a file name as the path argument.
>> I didn't know that. (Obviously.) The man page doesn't really say,
>> but all references to the path argument suggest that it contains a
>> directory or list of directories.
>> Nevertheless, the completion function for find (_find(), in
>> /etc/bash_completion.d/findutils or
>> /usr/share/bash-completion/completions/find) does expect that
>> argument to be a directory and expands only directories.
> I think I will need to deepen my knowledge into the bowels of unix.
> This thread is the first I've heard that completion depended on the
> command being typed. Thanks, all.
That's the reason for bash-completion package.
If you remove it, then the completion will fall back to generic behavior.
Andrey Repin (email@example.com) 20.09.2014, <8:26>
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple