Re: some unknown bug, says : command not found

[Greg Wooledge]

On Mon, Nov 01, 2021 at 06:34:45PM +0100, Alex fxmbsw7 Ratchev wrote:
> the hd one gives me, i think its the only two cat cases :
> 
> 00000410  0a 6d 76 20 2d 2d 20 22  24 74 74 22 20 22 24 74  |.mv -- "$tt"
> "$t|
> 00000420  74 74 22 0a 0a 24 78 62  6c 70 70 20 3c 28 0a 20  |tt"..$xblpp
> <(. |
> 00000430  69 66 20 5b 5b 20 2d 73  20 24 74 20 5d 5d 20 3b  |if [[ -s $t ]]
> ;|
> 00000440  20 74 68 65 6e 0a 20 20  63 61 74 20 2d 2d 20 22  | then.  cat --
> "|
> 00000450  24 74 22 0a 20 65 6c 69  66 20 5b 5b 20 2d 73 20  |$t". elif [[
> -s |
> 00000460  24 74 32 20 5d 5d 20 3b  20 74 68 65 6e 0a 20 20  |$t2 ]] ;
> then.  |
> 00000470  63 61 74 20 2d 2d 20 22  24 74 32 22 0a 20 65 6c  |cat -- "$t2".
> el|
> 00000480  73 65 0a 20 20 6b 6f 70  69 2e 67 61 77 6b 20 22  |se.  kopi.gawk
> 
> i cant really see, i gotta first code me an own hexdump in gawk

If you're sure this is the file that's causing the problem, the next
step is to figure out which *part* of the file is causing the problem.
You're showing a hex dump of one part, but this part looks reasonable,
at least as far as characters being within the expected ASCII range.