From: Andrew DeFaria <Andrew@DeFaria.com>
To: cygwin@cygwin.com
Subject: Re: perl -d causes completion to fail
Date: Mon, 20 Oct 2014 17:04:00 -0000 [thread overview]
Message-ID: <m23fb0$v3s$1@ger.gmane.org> (raw)
In-Reply-To: <20141020112344.GF9828@dinwoodie.org>
On 10/20/2014 4:23 AM, Adam Dinwoodie wrote:
> On Wed, Oct 15, 2014 at 03:08:42PM -0700, Andrew DeFaria wrote:
>> On 10/15/2014 2:30 PM, Andrew DeFaria wrote:
>> Adefaria-lt:ls /etc/bash_completion.d/perl
>> ls: cannot access /etc/bash_completion.d/perl: No such file or directory
>> Adefaria-lt:ls /usr/share/bash-completion/completions/perl
>> /usr/share/bash-completion/completions/perl
>> Adefaria-lt:
>>
>> I think you mean /usr/share/bash-completion/completions/perl... I
>> think the problem is that it's parsing the next token after -d and
>> -dt looking for :debugger and never things that maybe there's no
>> debugger name (see perldoc perldebug).
>
> Whatever you're using doesn't seem to be the Cygwin bash-completion
> package. Both x86 and x86_64 install /etc/bash_completion.d/perl:
>
> https://cygwin.com/packages/x86/bash-completion/bash-completion-1.3-1
> https://cygwin.com/packages/x86_64/bash-completion/bash-completion-1.3-1
>
> Before we go any further with anything else, I think your next step
> should probably be to install the Cygwin bash-completion package and
> check what the behaviour is there.
I ran setup and I see a "Keep" for 2.1-1 of bash-completion. I believe
that means it's already installed.
Additionally:
$ ls /usr/share/bash_completion.d/perl
ls: cannot access /usr/share/bash_completion.d/perl: No such file or
directory
$ ll /usr/share/bash-completion/completions/perl
-rw-r--r-- 1 adefaria Domain Users 3569 Feb 9 2014
/usr/share/bash-completion/completions/perl
$ cygcheck -f /usr/share/bash-completion/completions/perl
bash-completion-2.1-1
$
--
Andrew DeFaria
http://defaria.com
--
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-10-20 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 23:22 Andrew DeFaria
2014-10-15 18:47 ` Adam Dinwoodie
2014-10-15 21:31 ` Andrew DeFaria
2014-10-15 22:09 ` Andrew DeFaria
2014-10-20 11:23 ` Adam Dinwoodie
2014-10-20 17:04 ` Andrew DeFaria [this message]
2014-10-20 20:05 ` Ken Brown
2014-10-20 21:04 ` Andrew DeFaria
2014-10-22 14:50 ` Adam Dinwoodie
2014-10-22 17:09 ` Eric Blake
2014-10-22 17:09 ` Andrew DeFaria
2014-10-22 17:32 ` Ken Brown
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='m23fb0$v3s$1@ger.gmane.org' \
--to=andrew@defaria.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).