the last analyzement of the weirdness is
arr=( .. )
_alias_
then it at least runs thru one arr[0], which is set, and evals the code
right and working, however on the next [[ -v arr[1] ]] ( empty ) check it
hangs
if i dont write the newline after arr=( .. ) for like usual, i get hung on
already a
by second [[ -v arr[elem] ]] n after hangs i mean i have two parts in this
one is the kws index array with keywords to parse, the other is kws the
alias that parses the ${kws[@]} arr
so for the first element there in the last mail it worked
and displayed the content of the alias, as the code
but on
so i fixed the code to have a newline before using the kws alias
it, to my half surprise, works perfectly, it displays the metest keyword
right, but on the second [[ -v arr[elem] ]] check it hangs, probably brk
ing few then mmaping and unmapping much, == bug ? :)
bash-5.1# bash ogt_demo
+ bash
sorry for changing topics, i try .. its still the same topic code
the code (error, bug) is included in 'kws' which is supposed to eval set
keywords
i do
kws=( something ) kws
it hangs
i do
kws=( something ) ; kws
it hangs
i do only kws ( when the var is set already from last time ) it processes
n
