This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: No file name completion for file names start with underscore
- From: Paul.Domaskis <Paul dot Domaskis at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 25 Sep 2014 20:36:50 +0000 (UTC)
- 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> <357201998 dot 20140920082734 at mtu-net dot ru> <loom dot 20140925T001202-872 at post dot gmane dot org> <54234DC6 dot 3070302 at cs dot umass dot edu>
Eliot Moss <moss <at> cs.umass.edu> writes:
>On 9/24/2014 6:19 PM, Paul.Domaskis wrote:
>>Andrey Repin <anrdaemon <at> yandex.ru> writes:
>>>Paul.Domaskis wrote:
>> Can anyone suggest how the bash-completion man page is acccessed, and
>> what M-/ means?
>
> M is for "meta", as in the meta escape key functionality in Emacs.
> This will work according to the bash command line editing facility,
> etc. There are different ways to "make" meta-ness. One, if you
> set it up, is to use the Alt shift key. Another is to type the
> Escape key then the one that meta is being applied to, in this
> case, Escape then / (as two separate key strokes). I think given
> this information you can dig up more. I don't know where the
> documentation is on the bash completion package, off the top of
> my head.
>From googling, the meta key is Alt (simultaneously) or Esc (pressed
and released before the accompanying key). Using these to try and get
M-/, neither combination forces completion. In both cases, the entire
command line content is replaced by a forward slash.
I thought that the following .inputrc might be causing the problem:
.inputrc
--------
set visible-stats on
set editing-mode vi
So I renamed it to something else and launched some new cygwin
windows. Puzzlingly, the command line editing behaviour remains
unchanged. Not only does completion not work. So
find _vim<Tab>
doesn't complete even though _viminfo and _vimrc are present.
Similarly using of Alt or Esc for the meta key doesn't result in
completion when M-/ is typed. Much more puzzlingly, I can still get
vi editing behaviour at the bash command line. Very strange.
And the mystery doesn't stop there. If I open up an xterm, the above
completion *does* work using just the tab key. Woohoo! Very strange
that it would work, though -- it shouldn't!
However, the other anomalies are still present in the xterm. That is,
using Alt or Esc for the meta key in M-/ results in the entire command
line content being replaced by forward slash, and I also can get vi
editing behaviour at the bash command line.
Curioser and curioser....
--
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