> That is, when you write a new git command and forget to set execute > permission, you lose the "Permission denied" error. (Ditto if you > accidentally remove execute permission from an existing external git command.) True, but after getting the warning that 'git-frob' doesn't exist, it would probably only take a minute to figure out that 'git-frob' permissions need to be fixed, and then it's understandable why git choked on it. In contrast, it took me a while to discover my PATH permissions problem, and even then it wasn't clear why git should die because of a permissions problem on a directory that had little to do with git. Dale -- 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