From app-editors/vim-core: * To enable command-line completion for vim-core, run: * * eselect bashcomp enable vim-core * Calling eselect vi update... /usr/opt/portage/var/tmp/portage/app-editors/vim-core-7.1.285/temp/environment: /opt/portage/usr/bin/eselect: /bin/bash: bad interpreter: No such file or directory >>> app-editors/vim-core-7.1.285 merged. $ eselect bashcomp enable vim -bash: /opt/portage/usr/bin/eselect: /bin/bash: bad interpreter: No such file or directory After correcting the 'eselect' script to use "#!/bin/env bash": $ eselect bashcomp enable eselect !!! Error: /usr/share/bash-completion/eselect doesn't exist ... so even with the correct interpreter, eselect isn't looking within ${EPREFIX}/usr/share/
feels wrong indeed.... although I'm sure it worked an hour ago for me... Have to look into it.
(however, ESELECT_DATA_PATH within the script does look correct, being set as 'ESELECT_DATA_PATH="/opt/portage/usr/share/eselect/"'...) Looking more closely, there seems to be a widespread use of '${ROOT}' in the eselect scripts - where I'd expect to see '${PREFIX}'. Is this an obsolete usage, or should ROOT be set in my environment?
Created attachment 148106 [details, diff] eselect-1.0.11-r1.patch eselect-1.0.11-r1 is having src_unpack() twice. Unfortunately the first one is calling eprefixify. The attached patch merges both functions
Yep - that patch fixed it for me! (although there doesn't appear to be a completion file for 'vim-core', but there is one for 'vim'... is this a case where a line containing "${PN}" has accidentally been ported from vim to vim-core?)
Ahhh, that is an unfortunate merge-problem, I didn't notice. (Doing ~48 in half an hour sometimes is too much for me...) I applied the patch, thanks. re vim-core/vim: no looks fine, since vim-core is just a shared component between vim and gvim, whereas the former is the only one to be switched for other vi implementations.
