On Mon, 4 Nov 2024, 21:37 Robert Elz, wrote:
> | I guess I should s/POSIX/common Unix-like tradition/ and maybe
> | mumble something about BSD.
>
> you'd need to go to *every* OS that exists … Good luck with that.
Yeah I'm well aware this is futile whimsy.
I should have raised this point ab
On 11/3/24 10:45 PM, Martin D Kealey wrote:
This is one of those cases I would file under "POSIX being annoyingly literal".
POSIX says that the execve syscall reads the name of an interpreter (and
options) from a '#!' line, prefaces them onto the front of argv, and then
restarts itself. This i
Date:Mon, 4 Nov 2024 19:30:23 +1000
From:Martin D Kealey
Message-ID:
| I guess I should s/POSIX/common Unix-like tradition/ and maybe
| mumble something about BSD.
Yes, but this would not be the place where it is appropriate to
request system call changes - wha
Fair point. I guess I should s/POSIX/common Unix-like tradition/ and maybe
mumble something about BSD.
On Mon, 4 Nov 2024, 17:54 Robert Elz, wrote:
> Date:Mon, 4 Nov 2024 06:55:54 +0300
> From:=?UTF-8?B?T8SfdXo=?=
> Message-ID: <
> cah7i3lrjfhfgcejhmrmwd7mu2hu4r_oum
Date:Mon, 4 Nov 2024 06:55:54 +0300
From:=?UTF-8?B?T8SfdXo=?=
Message-ID:
| On Monday, November 4, 2024, Martin D Kealey
| wrote:
|
| > POSIX says that the execve syscall reads the name of an interpreter (and
| > options) from a '#!' line,
| >
|
| W
On Monday, November 4, 2024, Martin D Kealey
wrote:
> POSIX says that the execve syscall reads the name of an interpreter (and
> options) from a '#!' line,
>
Where?
--
Oğuz
This is one of those cases I would file under "POSIX being annoyingly
literal".
POSIX says that the execve syscall reads the name of an interpreter (and
options) from a '#!' line, prefaces them onto the front of argv, and then
restarts itself. This is why some people argue that ENOENT is "logical"
On 11/2/24 8:43 AM, hmms...@kpnplanet.nl wrote:
Bash Version: 5.2
Patch Level: 9
Release Status: release
Description:
If the interpreter after #! is wrong, a non-informative message prints
Repeat-By:
"unix2dos bashscript" starting with #!/bin/bash
./bashscript
bash
On 11/28/22 8:13 AM, H.Janssen wrote:
Bash Version: 5.2
Patch Level: 9
Release Status: release
Description:
If the interpreter after #! is wrong, a non-informative message is printed
Thanks for the report. This has been fixed in the devel git branch for a
while now.
--
``The lyf so short
