Re: Doesn't disambiguate between 'external command failed' and 'command not found'
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 6, 2011, 17:24 UTC
- Message-ID
- <7vpqlnmidy.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <20110705231604.GC12085@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I'm not all that happy with the advice, though. It's pretty technical > and specific. I'm not sure whether it would be helpful to most users or > not.
Yeah, Michael's rewording makes it fuzzier by saying "exists, unable to execute, maybe git-%s is broken?".
I notice that we do not give the path to the file that implements the command. Perhaps we should walk the $PATH after we see this failure to pinpoint which one is to be inspected (I vaguely recall a weatherbaloon patch to a similar effect)?