git/win32 at d8d3d632f4165955da49032d50279c20cfbde2e5 - git

Tree: d8d3d632f4

Andras Kucsma 05ac8582bc run-command: trigger PATH lookup properly on Cygwin On Cygwin, the codepath for POSIX-like systems is taken in run-command.c::start_command(). The prepare_cmd() helper function is called to decide if the command needs to be looked up in the PATH. The logic there is to do the PATH-lookup if and only if it does not have any slash '/' in it. If this test passes we end up attempting to run the command by appending the string after each colon-separated component of PATH. The Cygwin environment supports both Windows and POSIX style paths, so both forwardslahes '/' and back slashes '\' can be used as directory separators for any external program the user supplies. Examples for path strings which are being incorrectly searched for in the PATH instead of being executed as is: - "C:\Program Files\some-program.exe" - "a\b\c.exe" To handle these, the PATH lookup detection logic in prepare_cmd() is taught to know about this Cygwin quirk, by introducing has_dir_sep(path) helper function to abstract away the difference between true POSIX and Cygwin systems. Signed-off-by: Andras Kucsma <r0maikx02b@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>		5 years ago
..
alloca.h	…
dirent.c	…
dirent.h	…
git.manifest	…
lazyload.h	…
path-utils.c	…
path-utils.h	run-command: trigger PATH lookup properly on Cygwin	5 years ago
pthread.c	…
pthread.h	…
syslog.c	…
syslog.h	…
trace2_win32_process_info.c	…