Hi Leslie
>
> 1) Those of us who do not type 'rexx [execname]' would not like to
> have to
> learn to do that. :-)
No, I can see that. Note that in Linux, Mac, and other Unix derivatives, you
need to specify the full suffix on the filename, while on OS/2, VM and a well
adapted Wi
On 2018-11-16 09:19:07 René Jansen wrote:
> No, it is not, in the second example the env executable looks if there is a
> rexx on the path, the first looks for a /usr/bin/env/rexx executable.
>
> My proposal:
>
> Let’s get rid of the shebang; it outlived its usefulness
>
> 1) most people I know typ
exactly. That shebang does not warrant the effort.
> On 16 Nov 2018, at 11:45, Rick McGuire wrote:
>
> Seriously, these are SAMPLES. Fiddling with this falls pretty low on my list
> of priorities. If the amount of effort spent obsessing over the shebang lines
> in the samples had been applied
Seriously, these are SAMPLES. Fiddling with this falls pretty low on my
list of priorities. If the amount of effort spent obsessing over the
shebang lines in the samples had been applied to building an installer,
this issue would have been fixed ages ago.
Rick
On Fri, Nov 16, 2018 at 10:37 AM Ren
If we leave it in, it should be correct; because we (going forward) do not know
where the rexx executable is going to be installed (and the shebang is one
reason for that ongoing discussion), we should either use /usr/bin/env, which
will figure it out, or we need to correct the examples while in
On Fri, Nov 16, 2018 at 10:19 AM René Jansen wrote:
> No, it is not, in the second example the env executable looks if there is
> a rexx on the path, the first looks for a /usr/bin/env/rexx executable.
>
> My proposal:
>
> Let’s get rid of the shebang; it outlived its usefulness
>
> 1) most peopl
No, it is not, in the second example the env executable looks if there is a
rexx on the path, the first looks for a /usr/bin/env/rexx executable.
My proposal:
Let’s get rid of the shebang; it outlived its usefulness
1) most people I know type rexx [exec name]
2) on windows there is a mechanism
Dear developers,
is the shebang #! /usr/bin/env/rexx the same as #! /usr/bin/env rexx ?
The reason I ask is that I have a file WinUtils.cls where the former is present
and the latter seems to be the preferred option in CMakelists.txt
If I want to collect the latest/current tools used when crea
