Summary: | bash-completion does not complete correctly for "cvs commit" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Remy Blank <remy> |
Component: | Current packages | Assignee: | Gentoo Shell Tools project <shell-tools> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | A possible fix to /etc/bash_completion |
Description
Remy Blank
2005-01-17 16:01:37 UTC
Created attachment 48795 [details, diff]
A possible fix to /etc/bash_completion
This patch to /etc/bash_completion seems to fix the behaviour of "cvs commit".
However, I'm not yet sure if it breaks someting else for cvs auto-completion.
I'll report back after a few days of use.
Please try the latest version (I've just committed 20050112-r1). It has much improved cvs commit completion code. I'm afraid the symptoms with "cvs commit" are still exactly the same (using app-shells/bash-completion-20050112-r1). The patch still seems to work, too. Ok, this is what I am going to do for the solution. Since your "actual results" and "expected results" are both valid CVS commands, I really don't want to choose one or the other. Instead, I will be fixing it so that no space is appended to the directory name. This way, if you wanted to commit the dir as a whole (cvs ci dir) you can just hit enter. If you want to commit something *in* dir, then you can manually append the '/' and finish completing. 20050120 was just released today, so my fix will be included in the version bump. Bah, scratch that as I found a better solution ;) 20050120 is in cvs. Thanks for the report. |