DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=B2kxCSDU/6xmW9w5
	fE8o3b6V35W8iOzFKhSVBAYebo2cR1uWEvNVa5awl8m+jyW8ojuO5rumobPHIJW8
	Qax88+mb/5KT5UZBcKVH5V7Aqz7MEZxd8DgC6f/x0vreLz4wucdNhJ8tpvIvQV08
	ROLLMkSg20UMIn5y7Sxv2EVjSKE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sat, 20 Sep 2014 08:27:34 +0400
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <357201998.20140920082734@mtu-net.ru>
To: "Paul.Domaskis" <Paul.Domaskis@gmail.com>, cygwin@cygwin.com
Subject: Re: No file name completion for file names start with underscore
In-Reply-To: <loom.20140919T233113-212@post.gmane.org>
References: <loom.20140918T010225-301@post.gmane.org>   <loom.20140918T011028-898@post.gmane.org>  <loom.20140918T012259-677@post.gmane.org> <20140918000242.GA17489@phoenix>  <CACUHbYP+hmbvkVK_dO_C6H3QMLO3zGH+sK2fSovHox3XLUsWUQ@mail.gmail.com>  <lvf9re$l0j$1@ger.gmane.org> <loom.20140918T223627-193@post.gmane.org>  <20140918221943.GA22077@phoenix> <loom.20140919T233113-212@post.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Paul.Domaskis!

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


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 20.09.2014, <8:26>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple