Hello Gavin & Eli, I share the opinon by Gavin that it should not affect Cygwin, but to be frank, since I don't have Cygwin on my machine, I cannot test & confirm.
I tried to pull Gavin's update, but I came accross this : the file tta/perl/t/results/init_files_tests/documentation_examples/res_html/index.html seems to exist both as index.html and Index.html, and appears as modified to git, whereas I did not change it. git stash cannot clean this up, however I could clean it up with git reset --hard origin/master. So, finally I could test your change under MSYS/MINGW2 and it worked fine, even with an abosolute path, meaning that texi2dvi does not jeopardize MSYS euristic to convert paths. For the WSL, I think that the simplest solution would be to make some wrapper of texi2dvi that would make the correct file path translation. Vincent. ________________________________ De : Gavin Smith <gavinsmith0...@gmail.com> Envoyé : vendredi 18 avril 2025 15:01 À : Vincent Belaïche <vincent....@hotmail.fr> Cc : Eli Zaretskii <e...@gnu.org>; bug-texinfo@gnu.org <bug-texinfo@gnu.org> Objet : Re: Making texi2dvi working better on Microsoft Windows 10 On Fri, Apr 18, 2025 at 09:24:51AM +0000, Vincent Belaïche wrote: > Dear Gavin, Eli & Patrice, > > Yes, sorry, I should have done two different patches. Concerning the > MSYS2+MINGW64 console, this is only the first change that does the job, > ie handling "cygwin" same as "msys" when testing $OSTYPE. > > > Am I correct in saying for this MSYS2 console, OSTYPE is "cygwin", but > > the output of "uname" does not contain the string "cygwin"? Does the > > output of "uname" contain anything else that we could check for in > > addition to "cygwin" and "msys"? > > Yes, you are correct, in this MSYS2+MINGW64 console, uname outputs : > > MINGW64_NT-10.0-19045 > > in the MSYS2+MSYS console, uname outputs : > > MSYS_NT-10.0-19045 > > And in the MSYS2+MINGW32 console uname outputs : > > MINGW32_NT-10.0-19045 I have made the first change. I trust this is correct for whatever an "MSYS2+MINGW64" console is. I always find these combinations of systems bewildering. I don't expect this would change anything on Cygwin as this change is making an exception to using ";" as the path separator, using ":" in more cases.
