Thanks for the link and the additional information. I have stumbled upon a website with meticulous research about the unspecified shebang behavior across a wide range of systems:
https://www.in-ulm.de/~mascheck/various/shebang/ There's indeed so many variants that it may not be a good idea to do any modifications, here. Of course the portable solution you mentioned is also fine (performance is no issue on my stone-age shared host with just a handful of personal repositories). > So, I would expect both of the following to work: > #!/usr/bin/env -S fossil2/fossil cgi fossil.config > #!/user/bin/env -S fossil1/fossil cgi fossil.config No, they don't, as the CGI script name is appended as an extra argument to the shebang command line, causing Fossil to leave the path with the explicit "CGI" command. I was suggesting that Fossil keep going the explicit "CGI" command path even if there's more than three command line arguments. http://fossil-scm.org/index.html/artifact/5105d4bc1b?ln=1834 --Florian _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
