Re: [PATCH] run-command.c: Accept EACCES as command not found
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 21, 2011, 23:54 UTC
- Message-ID
- <7v62idf2vy.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <op.v5bjtk1r0aolir@keputer>
"Frans Klaver" <fransklaver@gmail.com> writes:
Show 13 quoted lines
> Actually I went through diagnosing and fixing it. After tracking it > down, I did wonder about this question myself and I didn't come to a > definitive conclusion on it. On one hand I do agree that it may be an > incentive for the user to fix his path. On the other hand I found it > an obscure one to track down; git's behavior doesn't match bash > behavior: > > $ git config --global alias.aliasedinit init && > mkdir searchpath && chmod 400 searchpath && > PATH=$(pwd)/searchpath:$PATH && export PATH && > mkdir someproject && cd someproject && > git aliasedinit > fatal: cannot exec 'git-aliasedinit': Permission denied
Imagine you did not have alias.aliasedinit in ~/.gitconfig but had a script called $(pwd)/searchpath/git-aliasedinit which we would fail to execute. What message would we get in that case? Currently I think we get permission denied.
Would we get the same with your patch, or something that does not hint at all that there is a permission problem?
See also the "tangent" part of
http://thread.gmane.org/gmane.comp.version-control.git/171755
and the discussion that follows it. I do not think we reached any conclusion nor a patch.