> Is this by design, or a bug? I currently do not see a reason for git stop executing an alias just because it cannot access a directory in PATH. Strangely, I also haven't found any discussion about this on the mailing list yet. If you look at start_command(), `git br` ends up as execvp call returning EACCESS in the given case whereas only ENOENT was "expected". This happens before git tries to resolve the alias. Could it be a legit assumption that PATH holds only accessible paths? (POSIX?) Otherwise it's a bug. -- 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