Date:Wed, 5 Oct 2022 15:36:55 -0400
From:Chet Ramey
Message-ID: <3d89acac-4c0a-64c9-e22c-1a3ca6860...@case.edu>
| Other than that, there's no advantage.
There can be. I have, on occasion (not in bash - I don't
write bash scripts) had a need to redefine one of
On 10/5/22 3:32 PM, Daniel Castro wrote:
In this case I’m not doing anything too fancy: my use case is I have a main
project script where I declare functions that can get executed
independently with some prefix: e.g. ``x.build()``, ``x.test()`` so I can
call ``myscript test`` or ``myscript
In this case I’m not doing anything too fancy: my use case is I have a
main project script where I declare functions that can get executed
independently with some prefix: e.g. ``x.build()``, ``x.test()`` so I
can call ``myscript test`` or ``myscript build`` by parsing all x.*
On 10/2/22 4:51 AM, Daniel Castro wrote:
Bash Version: 5.0
Patch Level: 17
Release Status: release
Description:
declare -F yields the wrong line number for a function that has
nested functions declared within. Instead it gives the line number of
the last
BASH PATCH REPORT
=
Bash-Release: 5.2
Patch-ID: bash52-001
Bug-Reported-by:Emanuele Torre
Bug-Reference-ID:
Bug-Reference-URL:
BASH PATCH REPORT
=
Bash-Release: 5.2
Patch-ID: bash52-002
Bug-Reported-by:Kan-Ru Chen
Bug-Reference-ID:
Bug-Reference-URL:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021109
Bug-Description:
