Description
Is your feature request related to a problem? Please describe.
Bash completion is a standard thing in any shell environment. Everybody depends on it. homebrew/Linuxbrew installs set this up automatically (except people have to configure their profile to make sure it's included).
However, we've never provided this explicitly for Windows... mostly because I didn't know if could work. But it works fine. There's just not a global technique to bring in the completions (that I know of).
Describe the solution you'd like
- ddev generates a ddev_bash_completion.sh for each release. It's bundled with each tarball.
- That can actually be placed anywhere, but probably the best place is /etc/bash_completion.d/ddev, (/etc/bash_completion.d may have to be created). (This assumes the use of git-bash)
- The user has to load it in their .profile or .bash_profile or wherever.
source /etc/bash_completion.d/ddev
- so we'd have to prompt them to do that.
I think the installer could do this pretty easily. It's conceivable that the installer could go looking for the .profile or .bash_profile, but IMO it's best to prompt people to do this.
I think this would be a big step forward for ddev on Windows.