CHchubot·Sep 24, 2018
I'm working in this area right now if you want to help :)
http://www.oilshell.org/
I took a survey of what people use here: https://lobste.rs/s/z96uyr/survey_what_shell_completion_scri...
That produced a link to this old project which tried to do something like what you want: a completion system that works for multiple shells (in this case, by code generation from a DSL)
https://github.com/mbrubeck/compleat
It's easy for you to say "completion should be specified in the binary" without actually specifying HOW. That's not straightforward, although I agree it's a good goal.
-----
Right now I'm implementing a bash-compatible completion API, and I'm actually getting pretty far without too much code. git-completion.bash is 3000 lines of code, so it's actually easier to emulate bash (with all its warts) than to write an entirely new completio
Read the rest
n system AND THEN write 3000+ lines of git completion in that hypothetical system.
https://github.com/oilshell/oil/issues/175
FWIW git is also the biggest completion script in the zsh source tree by a factor of 2 -- ~7000 lines IIRC with the next largest being around ~3000 lines.
Eventually Oil should have something better than bash completion, but the first step is taking advantage of ~40K lines of existing code in the bash-completion [1] project. I also looked at emulating zsh but that would be a lot more work than emulating bash.
[1] https://github.com/scop/bash-completion