From: Gary Johnson <garyjohn@spocom.com>
To: cygwin@cygwin.com
Subject: Re: No file name completion for file names start with underscore
Date: Thu, 18 Sep 2014 22:55:00 -0000 [thread overview]
Message-ID: <20140918221943.GA22077@phoenix> (raw)
In-Reply-To: <loom.20140918T223627-193@post.gmane.org>
On 2014-09-18, Paul.Domaskis wrote:
> Andrew DeFaria <Andrew <at> DeFaria.com> writes:
> >On 9/18/2014 11:42 AM, David Boyce wrote:
> >>> The path argument to find must be a directory.
> >>
> >> Sorry, but I can't let this go by. The statement above is
> >> incorrect, as a simple test like "find /etc/passwd -print" would
> >> show.
> >
> > Or just "find /etc/passwd". (-print has been the default for
> > decades... The man page it's the default but you should proob)
>
> Maybe things have changed. I think Gary Johnson is right.
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.
Regards,
Gary
--
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
next prev parent reply other threads:[~2014-09-18 22:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 23:13 Paul.Domaskis
2014-09-17 23:30 ` Paul.Domaskis
2014-09-18 0:03 ` Paul.Domaskis
2014-09-18 0:29 ` Gary Johnson
2014-09-18 18:51 ` David Boyce
2014-09-18 20:54 ` Andrew DeFaria
2014-09-18 21:32 ` Paul.Domaskis
2014-09-18 22:55 ` Gary Johnson [this message]
2014-09-20 3:02 ` Paul.Domaskis
2014-09-20 11:14 ` Andrey Repin
2014-09-24 23:03 ` Paul.Domaskis
2014-09-25 0:09 ` Eliot Moss
2014-09-25 22:13 ` Paul.Domaskis
2014-09-26 7:30 ` Eliot Moss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140918221943.GA22077@phoenix \
--to=garyjohn@spocom.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).