hello mates, when will you recode gawk to reably check for one RS already reached

[Alex fxmbsw7 Ratchev]

remember the case with tcpserver and gawk not able to read \r?\n for
buffering
it even happens worsly i think in my old code at least the new didnt use
gawk anymore
a back ssh bash script, spawns bash locally and makes it available via io
fifos locally and remotely via ssh fifos too with cat

it has a catch to catch control-c and if so it prints ee , one e for esc
and second also so just so cause its two bytes format
the other reads user typed to c%s "$char" .. to transmit

firstly it has an error the script and it doesnt have gawk so i wont post
but firstly it had an error about bash's input being c%s instead of %s by
the back transformer

and i had a transformer and back one and, didnt get reliable results

neaning

the RS if RS got recognized code of you doesnt catch
like demo'ed a bit in the earlier help-gawk (im not subscribed sorry ii
will err .. ) post

in which this behavior saying is so in code error, and it wont get fixed

i must move away from gawk, i was hoping it was cool, the more complete
awk... but this is totally nowork