> Am 12.03.2025 um 12:44 schrieb Michael Lueck <mlu...@lueckdatasystems.com>: > > Greetings Rony, > > > Rony G. Flatscher wrote: >> As such I would assume to be safe to add the hashbang "#!/usr/bin/env rexx" >> as the first line directly to all those files that you found not to have it. >> Then all Rexx scripts would adhere to the >> hashbang pattern. >> > > > Is calling env the multi-ooRexx instance safe method? > > I have always set my value based on the result of: > > $ which rexx > /usr/local/bin/rexx > > > Also a last step (beyond adding the hashbang) is on Linux file systems, > setting the Rexx scrip file to be executable. >
This is actually taken care of automatically when the hashbang is included (as it is for most samples). The warning I saw on CentOS actually do the opposite: for the samples missing the hashbang the installer REMOVES the executable bit from the file. This was the reason of my original bug report. > > I am thankful, > > -- > Michael Lueck > Lueck Data Systems > http://www.lueckdatasystems.com/ > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
