i checked the file with bvi, i dont see anything 2a 20 20 63 61 nothing, its a bash bug somewhere no ? none tried ?
On Wed, Nov 3, 2021, 11:33 Alex fxmbsw7 Ratchev <fxmb...@gmail.com> wrote: > xble='declare -p xblpp' . xbl > > bash: : command not found > declare -- xblpp="." > > this means the $xblpp is at end set to the right, as set on the beginning > but it still says and set -x es '' <( ., ) instead of . or cat <( .. ) > > anyone any idea ? > > see chet such ( masswise ) i meant with unreported hogging bugs > > On Tue, Nov 2, 2021, 13:53 Alex fxmbsw7 Ratchev <fxmb...@gmail.com> wrote: > >> but how why or to fix >> thers the code, thers the set -x parts >> >> ++ xblpp=. >> .. >> ++ '' /dev/fd/63 >> >> On Tue, Nov 2, 2021, 13:49 Alex fxmbsw7 Ratchev <fxmb...@gmail.com> >> wrote: >> >>> i dont have "$var" <( sub ) i have $var <( sub ) >>> else it makes sense >>> >>> On Tue, Nov 2, 2021, 13:42 Greg Wooledge <g...@wooledge.org> wrote: >>> >>>> On Tue, Nov 02, 2021 at 04:52:24AM +0100, Alex fxmbsw7 Ratchev wrote: >>>> > to answer around what was written, i dont have a cat alias >>>> > >>>> > but what mr andreas wrote seems much similiar to what i do, process >>>> sub.. >>>> > ill check the vars carefully but i dont get it fully >>>> >>>> unicorn:~$ bash >>>> unicorn:~$ $xyz <( true ) >>>> bash: /dev/fd/63: Permission denied >>>> unicorn:~$ "$xyz" <( true ) >>>> bash: : command not found >>>> >>>> > but, on your all tries to produce command not found, can u set -x the >>>> > tries, .. in mine it shows ++++ cat ... then command not found, like >>>> the >>>> > cat is gone somehow >>>> > means does yours produce a + cat ( or cmd ) and then just display >>>> command >>>> > not found >>>> >>>> unicorn:~$ bash >>>> unicorn:~$ set -x >>>> unicorn:~$ "$xyz" <( cat /dev/null ) >>>> + '' /dev/fd/63 >>>> ++ cat /dev/null >>>> bash: : command not found >>>> >>>> I don't know what else to tell you. Your customized environment is so >>>> ridiculously convoluted that NOBODY understands it, not even you. >>>> >>>> Either this is helpful, or not. I don't think you're going to get any >>>> better results from help-bash or bug-bash than this. >>>> >>>> In any case, I'm 99% sure this is not a bug in bash -- only in one of >>>> your files. >>>> >>>>
