On Mon, Sep 15, 2025 at 04:25:07PM -0400, Chet Ramey wrote:
> On 9/13/25 5:45 AM, Mike Jonkmans wrote:
> > On Fri, Sep 12, 2025 at 04:31:07PM -0400, Chet Ramey wrote:
> > > On 9/11/25 5:02 PM, Mike Jonkmans wrote:
> > > > The below script echoes (when saved to bash_command.bash):
> > > > Trace:
> >
On 9/13/25 5:45 AM, Mike Jonkmans wrote:
Thanks for your answers.
On Fri, Sep 12, 2025 at 04:31:07PM -0400, Chet Ramey wrote:
On 9/11/25 5:02 PM, Mike Jonkmans wrote:
The below script echoes (when saved to bash_command.bash):
Trace:
1: bash_command.bash:29 onerror ()
2: bash_command.ba
Thanks for your answers.
On Fri, Sep 12, 2025 at 04:31:07PM -0400, Chet Ramey wrote:
> On 9/11/25 5:02 PM, Mike Jonkmans wrote:
> > The below script echoes (when saved to bash_command.bash):
> > Trace:
> >1: bash_command.bash:29 onerror ()
> >2: bash_command.bash:29 mymain ()
> >3: bas
On 9/11/25 5:02 PM, Mike Jonkmans wrote:
Hi,
The below script echoes (when saved to bash_command.bash):
Trace:
1: bash_command.bash:29 onerror ()
2: bash_command.bash:29 mymain ()
3: bash_command.bash:31 main ()
mymain: 29 status=1 command=return 1.
1) BASH_COMMAND is foo's 'return 1'.
Hi,
The below script echoes (when saved to bash_command.bash):
Trace:
1: bash_command.bash:29 onerror ()
2: bash_command.bash:29 mymain ()
3: bash_command.bash:31 main ()
mymain: 29 status=1 command=return 1.
1) BASH_COMMAND is foo's 'return 1'. Shouldn't that be 'foo'?
There is no error
Date:Thu, 11 Sep 2025 23:02:16 +0200
From:Mike Jonkmans
Message-ID: <20250911210216.ga164...@jonkmans.nl>
| 1) BASH_COMMAND is foo's 'return 1'. Shouldn't that be 'foo'?
That I will leave for someone else.
|There is no error in 'return 1' per se.
Not releva