You can do "chown mattdm.ap[tab]", but "chown mattdm:ap[tab]" results in "chown apache" (oops!). This is particulary odd because if you do "chown mat[tab]" you get "chown mattdm: " with a : on the end.
I can't reproduce this on F-8, 20060301-10. Sound similar as bug 444466, maybe something's changed wrt. colon handling in F-9/Rawhide bash?
On a CentOS 5 box (which is to say, circa FC6) with bash-completion-20060301-10 rebuilt and installed I get different misbehavior -- it completes 'chown mat[tab]' to "chown mattdm\: ", and then if I backspace and hit tab again I see all the group options but if I then continue with 'chown mattdm\:mat[tab]' it completes that to "chown mattdm\\\:mattdm", which of course is also wrong. So I agree, *something* has changed. But it wasn't right before either. :)
That's what I see on F-8 too, but I'd like to first concentrate on the regression, then see if something could be done to the original issue. Could you post your F-9 output with set -x for "chown mattdm:apa[TAB]"? As said I suspect this is the same issue as #444466 but the output there (thanks btw) is quite complicated, this test case could produce a simpler one.
$ chown mattdm:apa+ local cur + cur=mattdm:apa + [[ mattdm:apa == -* ]] + _count_args + args=1 + (( i=1 )) + (( i < COMP_CWORD )) + case $args in + _usergroup + local 'IFS= ' + cur=mattdm:apa + [[ mattdm:apa = *@(\\:|.)* ]] + [[ mattdm:apa = *:* ]] + '[' -n '3.2.33(1)-release' ']' + COMPREPLY=($( compgen -g -- ${cur##*[.:]} )) ++ compgen -g -- apa apache
Damn, I have no clue what might be causing this. The output I get on F-8 is exactly the same as yours except for the last line, yours is "<TAB>apache" (or maybe <TAB> is 8 spaces), mine is "che": - apache +che ...and there's nothing between the F-8 and devel bash packages that would look like a possible culprit, there's just one trivial .bash_logout change and a GCC 4.3 rebuild. And I can't reproduce in a mock Rawhide x86_64 shell either. Ideas?
*** This bug has been marked as a duplicate of 444466 ***
I'm gonna reopen this one, because while the problem with it entirely eating the word does seem to be gvfs's fault, the incorrect behavior in Comment #2 is still there.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Bug 444466 deals with the gvfs issue, so I suppose this should be assigned back to bash-completion. Or actually, based on the info I've been able to find, perhaps to bash itself or closed CANTFIX, see e.g. http://bugs.gentoo.org/show_bug.cgi?id=67108#c5 . Thoughts?
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This has been fixed after bash-completion 1.1 upstream; the next version (which I hope isn't that far in the future) should contain the fix.
bash-completion-1.2-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/bash-completion-1.2-1.fc13
bash-completion-1.2-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
bash-completion-1.2-3.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/bash-completion-1.2-3.el5
bash-completion-1.2-4.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.