Well, as regards the detection of shell and the rest we just need to bundle the bash completion script in PEAR tarball, in a folder which we’d put community contributed scripts, tools, docs or something else, then upon the installation Distro would decide where to place the script and activate it in case (e.g., in Gentoo bash-completion USE flag would do the trick).

And I agree with Helgi on the fact that it’s totally static, right now I’m not aware of any good (good as being available everywhere there’s a bash and gnu core utilities) way to rapidly parse an XML file and provide different options as user touches the Tab key, though it makes things even more tricky, since we need to locate commands XML files and …, Or another workaround could be a verbose option for “pear help”. Parsing it’s output would be rather easy.

One thing I have a bit of beef about the script is it is all static atm, I’d like to see at least a script to regenerate the info from the arrays in each command class or even just the XML classes (they are all up2date, last time I checked anyway), I’ll think about this and see if I can provide a solution for this that would be suitable.