public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: George Prekas <prekgeo@yahoo.com>
To: cygwin@cygwin.com
Subject: Re: bash / readline problem with cd, directories with spaces, nospace
Date: Thu, 19 Mar 2015 16:04:00 -0000	[thread overview]
Message-ID: <meeo1u$3su$1@ger.gmane.org> (raw)
In-Reply-To: <f5bwq38a9lm.fsf@troutbeck.inf.ed.ac.uk>

On 23/02/2015 17:14, Henry S. Thompson <ht@inf.ed.ac.uk> wrote:
> [OK, here's the message body I _thought_ I sent with the cygcheck
> output which is all that appears to have been received...]
>
> I _think_ this is a regression, but my memory for this sort of thing
> is terrible.
>
> With libreadline7-6.3.8-1, given that I have
>
>   /c/Program Files
>   /c/Program Files (x86)
>   /c/ProgramData
>
> If I type
>
>   > cd /c/Prog[tab]
>
> I get [bell/flash] and
>
>   > cd /c/Program
>
> All correct so far
>
>   > cd /c/Program[tab]
>   [bell/flash]
>   > cd /c/Program[tab again]
>   Program Files/    Program Files (x86)/    ProgramData/
>   > cd /c/Program
>
> Still as expected
>
>   > cd /c/Program\ [tab]
>   [bell/flash]
>
> _Not_ as expected, should give
>
>   Program Files/    Program Files (x86)/
>   > cd /c/Program\ Files
>
> Overriding the standard (Linux too, where I cannot reproduce the problem)
>   complete -o nospace -F _cd cd
> with
>   complete -o default -F _cd cd
> fixes this, but I don't _think_ it used to happen.
>
> Related (?) problem
>
>   > cd /c/'Prog'[tab]
>
> should result in
>
>   > cd /c/Program
>
> but in fact just gives [bell/flash]
>
> Can anyone reproduce, either correct behaviour with earlier readline
> and/or earlier bash-completion than 1.3-1, or same problem as me?
>
> Or have I inadvertently screwed something up?
>
> Thanks
>
> ht
>

Hi Henry,

I had the same trouble as you describe and I was using your workaround, 
but then I realized that find is broken in the same way.  So, I did some 
research and found out that Debian and Ubuntu have solved this problem 
by patching /etc/bash_completion as described in the following URLs:

<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739835>

<https://code.launchpad.net/~jjo/bash-completion/quote_readline_by_ref_fixes/+merge/210930>

I think Cygwin should incorporate the specified patch file in its 
bash-completion package.

Regards,
George


--
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:[~2015-03-19 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 17:34 Henry S. Thompson
2015-02-23 17:42 ` Henry S. Thompson
2015-03-19 16:04   ` George Prekas [this message]
2015-03-19 17:53     ` Henry S. Thompson
2015-03-19 19:05       ` Eric Blake

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='meeo1u$3su$1@ger.gmane.org' \
    --to=prekgeo@yahoo.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).