[Bash-completion-devel] [bash-completion-Bugs][312610] simple directory completion kills local echo under certain circumstances

[bash-completion-bugs at alioth.debian.org]

Bugs item #312610, was changed at 2010-06-28 01:33 by Ville Skyttä 
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312610&group_id=100114

Status: Open
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: simple directory completion kills local echo under certain circumstances 
Distribution: None
Originally reported in: None
Milestone: None
Status: None
Original bug number: 


Initial Comment:
Anonymous message posted by costa _AT_ mouldwarp _DOT_ com

The buggy scenario is as follows:

$ rm -R a_read_only_dir<TAB>/<ENTER>
override r-xr-xr-x  user/user for a_read_only_dir? <CTRL-C>^C
$ # local echo is gone, that is, keyboard input ceases to print

I'm pretty sure both completion and rm do something with the terminal (sending escape codes), and here together they fail.

Although minor, pretty annoying - breaks backward compatibility. Found on Darwin.

----------------------------------------------------------------------

>Comment By: Ville Skyttä  (scop-guest)
Date: 2010-06-28 20:19

Message:
I cannot reproduce (Linux, bash 4.1.7), and I don't think bash-completion's rm completion sends any escape codes. Have you tried without bash-completion?

$ mkdir -m 555 foo
$ sudo chown root:root foo
$ rm -R foo<TAB>/<ENTER>
rm: remove write-protected directory `foo'? <CTRL-C>
# local echo continues to work

----------------------------------------------------------------------

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312610&group_id=100114