Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 254814 - app-shells/bash-completion - man page completion doesn't work properly with lzma compression
Summary: app-shells/bash-completion - man page completion doesn't work properly with l...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo Shell Tools project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 259724
  Show dependency tree
 
Reported: 2009-01-13 11:55 UTC by Jan Hruban
Modified: 2009-12-27 17:07 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
simple patch to fix above behaviour (bash-completion-man-lzma.patch,435 bytes, patch)
2009-01-13 14:25 UTC, Jan Hruban
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Hruban 2009-01-13 11:55:09 UTC
I've got set lzma compression for documentation by putting PORTAGE_COMPRESS="lzma" into /etc/make.conf
Because of this, bash completion for man command does not work properly.

Reproducible: Always

Steps to Reproduce:
1. put PORTAGE_COMPRESS="lzma" into make.conf
2. (re)install some package
3. try to tab-complete man command for some manpage from the (re)installed package

Actual Results:  
$ man cupsd<TAB>
cupsd.conf.5   cupsdisable.8  cupsd.8

Expected Results:  
$ man cupsd<TAB>
cupsd.conf   cupsdisable  cupsd
Comment 1 Jan Hruban 2009-01-13 11:57:50 UTC
Forgot to mention - I've noticed this behaviour in version app-shells/bash-completion-20060301 and it persists in newest testing app-shells/bash-completion-20081218
Comment 2 Jan Hruban 2009-01-13 14:25:30 UTC
Created attachment 178366 [details, diff]
simple patch to fix above behaviour
Comment 3 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2009-02-20 05:31:53 UTC
(In reply to comment #2)
> Created an attachment (id=178366) [edit]
> simple patch to fix above behaviour
> 

Confirmed it is already fixed upstream and confirmed it is a problem for us. Patched in bash-completion-20081218-r1

Thanks!