Tush truncates a byte in script at byte index 8192

[GuillaumeHM]

Hello there,

First, thank you for this simple and effective tool.

I have a tush script which size is greater than 8192 (8209 bytes). When I run it, it shows differences between written and executed commands in its output:

-$ cmp --ignore-initial=1023 file_1 file_2
+$ cmp --ignore-initial=103 file_1 file_2

A byte is missing in executed command, so the command fails and leave me with a true-negative result. That byte is the 8193th...
So I guess a maximum string length or buffer size is reached. The strange thing is that next bytes are ok ! Only one is missing.
If I add bytes before in the script, the missing byte differ accordingly (always the 8193th misses).

I see only one workaround: split the script in two scripts. That makes quite a short script limit : 8192 bytes...

Running on Debian bullseye; getconf ARG_MAX returns 2Mo. Is that limit inside awk ?

I'm ready to help on that.