Made me want to give a shot at writing a custom bash completion script for an internal tool (having a lot of sub-sub-commands and many options, kind of like git

Made me want to give a shot at writing a custom bash completion script for an internal tool (having a lot of sub-sub-commands and many options, kind of like git). How hard could that be? Then I looked at git-completion.bash [1] and suddenly all my motivation vanished. Maybe Fig found a more declarative way of describing a tool's syntax? [1] https://github.com/git/git/blob/master/contrib/completion/git-completion.bash https://github.com/git/git/blob/master/contrib/completion/gi...