Your message dated Sun, 17 Apr 2011 13:23:03 -0500
with message-id <[email protected]>
and subject line Re: Bug#618303: bash-completion: adds "<space>" rather than "/"
has caused the Debian Bug report #618303,
regarding bash-completion: adds "<space>" rather than "/" after "cp 
directory<tab>"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
618303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618303
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash-completion
Version: 1:1.3-1
Severity: normal


This is a regression from 1.2-3.

I have a directory named "directory"

cp directory<tab>

completes with a space as if there are no other possibilities (i.e. it
does not give the opportunity to further specify directory contents
without first typing backspace and then "/").

Kevin

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'testing'), (400, 'stable'), (300, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.34.8.000 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bash-completion depends on:
ii  bash                          4.1-3      The GNU Bourne Again SHell

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Dear Kevin,

On Sun, Apr 17, 2011 at 11:12:59AM -0700, Kevin Mitchell wrote:
> On Sat 11.04.16 05:30, Kumar Appaiah wrote:
> >Do you have Adobe's Acrobat? In other words, you have
> >/etc/bash_completion.d/acroread.sh?
> 
> weird, that seemed to fix it thanks.

Thanks for the confirmation. I am closing this bug.

Kumar

-- 
Kumar Appaiah


--- End Message ---

Reply via email to