From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: No file name completion for file names start with underscore
Date: Fri, 26 Sep 2014 07:30:00 -0000 [thread overview]
Message-ID: <5424CD19.5050105@cs.umass.edu> (raw)
In-Reply-To: <loom.20140925T221648-685@post.gmane.org>
On 9/25/2014 4:36 PM, Paul.Domaskis wrote:
> 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?
> 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.
>
Works for me, but I have 'set -o emacs' set in my bash. I wonder
if it is somehow dependent on using emacs style command line editing?
Regards -- Eliot Moss
--
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
prev parent reply other threads:[~2014-09-26 2:19 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
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 [this message]
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=5424CD19.5050105@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).