On Wed, Apr 26, 2023, 23:28 Grisha Levit <grishale...@gmail.com> wrote:
> If a parser error is encountered when `local' is parsing an array
> assignment string, the installed unwind-protects never run:
>
> $ f() { local -a a='(())'; }; f
> bash: syntax error near unexpected token `('
> $ declare -p a FUNCNAME
> declare -a a
> declare -a FUNCNAME=([0]="f")
>
> ----
>
> If there's a PROMPT_COMMAND set and a parser error is encountered during a
> compound assignment, the alias expansion state is not properly restored:
>
to mr chet
do u personally have an index of files , all ..
like a human format note from since ever
i come up once for my interest
secondly , its about modernizing bash , by background ..
imagine two three filled free text tiles
./runway
./related
./extra
to topic content of the code
1 i see this since i entered linux .. isnt changed yet .. this n that codes
, but me no clue about it
excepts they are oudated ...
.. i also changed my bash styles much , like improving , not sticking to
stupid old hangs
.. so many .tgz no well doc ..
i have to come up with some mixing code to auto make ( bash scripts ) to
make always updated code by singular parts
o .. if u could insight me in the devel tree or official tgz , some in-code
commons that i can parse off - any file info counts
the more info u write the more i can make autoparse code
.. me very good in this is
.. may be great .c beginnings for me
i remember writing 10 years ago parsers for lib parser tools .. when it was
hipp .. i sadly dont remember the details anymore
of course the results will be open source
greets , ikss
$ PROMPT_COMMAND=:; alias A=:
> $ declare a=(())
> bash: syntax error near unexpected token `('
> $ A
> bash: A: command not found
>
