Hi, I'd also like to help. I already have worked out some ideas about splitting up bash completion: - completions all reside in separate files - the completions are loaded dynamically - all completions initially go through a function '_comp_load()' - first time only - DejaGnu is used for automated testing - it scales
See: - http://code.google.com/p/bash-completion-lib/ (source) - http://fvue.nl/wiki/Bash_completion_lib (homepage) I'm halfway adding all completions from bash_completion and I'm curious what your thoughts are about the project and if it's the way to go? The next step would be to patch bash to include two features, see: http://groups.google.com/group/gnu.bash.bug/browse_thread/thread/281698132559a422/47217d83d4308d4e?lnk=gst&q=vulto#47217d83d4308d4e Then bash-completion-lib can be improved to be truly dynamic - without the need to define all the commands to complete on... :-) Regards, Freddy Vulto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
