Eli Zaretskii wrote: > > Cygwin does a similar thing; not inside bash but inside its fork+exec() > > system calls (which bash uses, of course). [4] > > Not entirely, because, for example, /dev/null is left unchanged.
Fortunately Cygwin does not do this sort of heuristic substitutions in argv[1..argc] — otherwise I couldn't recommend Cygwin either. > Also, drive letters are not handled, AFAIR, so invoking programs from > another drive could be problematic. That is acceptable; it's only a minor restriction for a developer and no restriction in a CI environment (which has only one drive, typically). Bruno
