public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Paul.Domaskis <Paul.Domaskis@gmail.com>
To: cygwin@cygwin.com
Subject: Re: No file name completion for file names start with underscore
Date: Thu, 18 Sep 2014 21:32:00 -0000	[thread overview]
Message-ID: <loom.20140918T223627-193@post.gmane.org> (raw)
In-Reply-To: <lvf9re$l0j$1@ger.gmane.org>

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.

For background, my old 32-bit cygwin 1.7.17-1 install (bash 4.1.10-4),
"cygcheck -cvs | grep -i completion" shows no packages with the string
"completion" in the name.  And if I have files (not directories)
_viminfo & _vimrc, tabbing after "find _vi" does a completion up to
"find _vim", then shows me the two candidate files thereafter.

In my new 64-bit cygwin 1.7.28-2 (bash 4.1.11-2, bash-completion
1.3-1), I also have _viminfo & _vimrc, but "find _vi" doesn't
complete, nor does it show candidate files.  I ensured that I have
directories vimfiles and vimtest, and "find vi" does complete up to
"find vim", then shows me the two candidate directories thereafter.

On the other hand, in the new 64-bit cygwin, "ls vi" and "ls _vi"
*always* completes as much as it can, then shows me the two candidates
thereafter.


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

  reply	other threads:[~2014-09-18 20:54 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 [this message]
2014-09-18 22:55             ` Gary Johnson
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=loom.20140918T223627-193@post.gmane.org \
    --to=paul.domaskis@gmail.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).