> From: Bruno Haible <br...@clisp.org> > Cc: gavinsmith0...@gmail.com, pertu...@free.fr, bug-texinfo@gnu.org > Date: Sun, 27 Oct 2024 21:21:27 +0100 > > 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.
MSYS only does that (and all the rest) when the program to be invoked is a native Windows program. > > 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). It can be a major PITA if you have several active drives, or if the /usr tree is mounted on drive C: while you are building something on drive D:.
