SZEDER GÃbor <szeder@xxxxxxxxxx> writes: > I think this is not necessary. We already run __git_aliases() every > time after 'git <TAB>', and it was not an issue so far. If we allow that line of reasoning, the cached $__git_all_commands that can go stale needs to be removed, no? I think folks running bash on windows wanted it and it would be helping them. One valid looking argument against caching aliases but still caching commands is that the former could change on the end user's whim while the latter is more or less stable across releases, but people can throw their own "git-frotz" in their path and run it as "git frotz", so that is not entirely a valid argument, either. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html