i completly dunno how to fix, it looks me like a bash bug due to unconsitency, .., i can try later on wsl2 on win11 debian, ..but ive had yet a lots of couple of inconsistency bugs like this, also to early startup symlink related i dont remember exactly anymore
On Tue, Nov 2, 2021, 06:07 Alex fxmbsw7 Ratchev <fxmb...@gmail.com> wrote: > .. regarding a $notset <( .. wouldnt that display in set -x on that line, > rather when the cat or gawk is ran > > On Tue, Nov 2, 2021, 06:03 Alex fxmbsw7 Ratchev <fxmb...@gmail.com> wrote: > >> i dont see the 63, its inside that tho >> >> i post the code, as i saw its fairly short, 'xbl' file >> the tgz with required awks and support files is also sent >> >> but anyway in the xbl the affected part are the cat or kopi.gawk if parts >> inside $xblpp <( here ) >> >> $xblpp is either cat or . >> cat for 'display me the code' and defaultly . for 'source the code, not >> display' >> $t and $t2 are just stamps, as seen in my set -x post >> >> i think this error came up recently just, it happens when i . xbl too >> new bash seasion sources it right without err, i never seen this err >> before too >> bash 5.1.8 debian release >> >> i think its some bug.. what else could it be, .. new bash sessions source >> it right, also before this err really wasnt, not that i tried . script >> instead of new bash sessions much >> >> .. >> >> On Mon, Nov 1, 2021, 23:08 Andreas Kusalananda Kähäri < >> andreas.kah...@abc.se> wrote: >> >>> On Tue, Nov 02, 2021 at 03:23:15AM +0700, Robert Elz wrote: >>> > Date: Mon, 1 Nov 2021 12:03:48 -0400 >>> > From: Greg Wooledge <g...@wooledge.org> >>> > Message-ID: <YYAP5PynR6Us/FV/@wooledge.org> >>> > >>> > | > bash: : command not found >>> > | > bash: : command not found >>> > | >>> > | Because this is you, I can't be sure whether you are correctly >>> pasting >>> > | the output from your terminal into email, >>> > >>> > Actually, because it is him, it is more likely that he has "cat" >>> aliased >>> > to ' ' somehow, since he loves aliases so much. >>> > >>> > kre >>> > >>> >>> Looking at their trace output, the thing that causes the error is >>> >>> '' /dev/fd/63 >>> >>> The /dev/fd/63 bit is probably from a process substitution. >>> >>> What causes the '' is anyone's guess, and mine is that it's simply a >>> variable that happens to be unset or empty (possibly due to a mistyping >>> in its name?) >>> >>> $ "$my_thnig" <( [[ -s "$pathname" ]] && cat -- "$pathname" ) >>> bash: : command not found >>> >>> >>> >>> -- >>> Andreas (Kusalananda) Kähäri >>> SciLifeLab, NBIS, ICM >>> Uppsala University, Sweden >>> >>> . >>> >>>
