| Summary: | app-shells/bash-3.2_p48-r1: [TAB] completion broken | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | bash-3.2-tab-completion-slash-fix.patch | ||
|
Description
Martin Mokrejš
2009-02-16 16:07:33 UTC
My previous last and working version was app-shells/bash-3.2_p48 Have you checked if thus is in all your shells? I have had similar problems when binary output was sent to stdout. yes, try restarting your shell. it isnt specific to bash-3.2_p48. some commands might screw up the shell state logic causing it to append slashes to regular files. easy way i found to reproduce was with svn: svn ps svn:ignore "$(svn pg svn:ignore ..)" . I have rebooted since the time and now cannot reproduce anymore. Probably some of you was right. ;-) Created attachment 183011 [details, diff]
bash-3.2-tab-completion-slash-fix.patch
Just for the sake of completeness, there was once posted a patch dealing with this problem to the bash-bug mailing list. I wasn't able to dig up the URL to the original posting but I used the attached patch since I read about the problem in that mailing list without any problems. AFAIR, Chet said this problem would be fixed with bash-4.0
|