Bug 14255 - file name completion via tab key broken for cvs commands
Summary: file name completion via tab key broken for cvs commands
Status: RESOLVED MOVED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Shlomi Fish
QA Contact:
URL: https://alioth.debian.org/tracker/ind...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-09 07:56 CEST by Charly Pammer
Modified: 2014-11-05 10:43 CET (History)
0 users

See Also:
Source RPM: bash-completion-2.1-5.mga4.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Charly Pammer 2014-10-09 07:56:31 CEST 
In bash-completion file name completion via tab key seems to be broken when using CVS commands.

For instance if I want to check the cvs log history for file "foo" invoking "cvs log f" followed by tab-key will not offer file "foo".

The completions file /usr/share/bash-completion/completions/cvs seems to be culprit. When I remove it (and open a new shell) tab completion for the file name work again.

As a consequence of this workaround, I loose the tab completion for cvs commands (e.g. "cvs lo" plus tab key will no longer be expanded to "cvs log").









Reproducible: 

Steps to Reproduce:
David Walser 2014-10-09 21:21:10 CEST

Assignee: bugsquad => shlomif

Comment 1 Shlomi Fish 2014-10-10 08:15:32 CEST 
Hi Charly!

Please report this problem upstream - http://bash-completion.alioth.debian.org/ .

Regards,

-- Shlomi Fish
Comment 2 Charly Pammer 2014-10-13 19:13:27 CEST 
Done.

Upstream bug is:
https://alioth.debian.org/tracker/index.php?func=detail&aid=314848&group_id=100114&atid=413095

URL: (none) => https://alioth.debian.org/tracker/index.php?func=detail&aid=314848&group_id=100114&atid=413095

Comment 3 Shlomi Fish 2014-11-05 10:43:44 CET 
Will now be tracked upstream. Thanks!

Status: NEW => RESOLVED
Resolution: (none) => MOVED
Note You need to log in before you can comment on or make changes to this bug.