Summary: | eix based emerge bash-completion alternative? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Imre Péntek <pentek.imre> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED CANTFIX | ||
Severity: | enhancement | CC: | raphael.droz+floss |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
patched routine
diff |
Description
Imre Péntek
2008-04-18 22:44:31 UTC
You could simply do `eix huns` and then use the results. Please reopen this bug when you have worked out how this should be implemented in bash-completion. Patches are welcome. Created attachment 156083 [details]
patched routine
Created attachment 156085 [details, diff]
diff
maybe there are other places when eix would be applicable, anyways this can be at least considered as a proof-of-concept about the fact eix can be used for this task. The rule of bash_completion is that the command being completed (or it's mandatory depedancies may be used to complete) [eg, perl completion can use perl, eix completion can use eix] But emerge cannot, anyway I think that using one of the following would be acceptable : [[ -x "$(whereis eix 2> /dev/null)" ]] or if $(type _eix 2>/dev/null); ... Then instead of using : for x in ${cat}/${pkg}/*.ebuild it would be, eg l.486 : eix -C ${cat} ${pkg} The second way of testing first needs the eix completion to be done... Maybe such thing would let (if desired) : emerge sys<tab> lists sys-, sysfsutils, sysload, ... and not only category beginning with sys ? (In reply to comment #4) > maybe there are other places when eix would be applicable, anyways this can be > at least considered as a proof-of-concept about the fact eix can be used for > this task. > |