send-text character limit

[jbrea]

Hi

I used to send large junks of code from vim to kitty via vim-slime.
vim-slime writes to ~/.slime_paste, and invokes kitty @ send-text --match id:ID --from-file ~/.slime_paste where ID is some window id.
Ever since I upgraded kitty to version 0.17.3 I cannot send anymore junks of code of more than 1024 characters.

Is there a way around this limitation?

[kovidgoyal]

I'm going ot need a way to reproduce this without need vim slime or
similar. I tried the following simple test

Created a file of 2048 bytes first 1024 a and then 1024 b

Ran kitty with kitty -o allow_remote_control=y

Inside kitty ran

kitty @ send-text --from-file filename

All 2048 bytes were transmitted

[jbrea]

Created a file of 2048 bytes first 1024 a and then 1024 b
Ran kitty with kitty -o allow_remote_control=y
Inside kitty ran
kitty @ send-text --from-file filename

I just tried the same. Nothing gets transmitted (unless I remove every b).
What kind of information can I provide to debug this?
I am on arch linux with kernel 5.6.7-arch1-1, i3 window manager 4.18.1 and python 3.8.2.

[kovidgoyal]

Run kitty from another terminal and see what error if any are printed
out. Have you enabled remote control?? Does sending simple text like

kitty @ send-text test

work?

[jbrea]

kitty @ send-text test

Yes, this works.

kitty @ send-text --from-file filename also works, if filename contains less than 1025 characters.

No error gets printed when I run kitty from another terminal.

[kovidgoyal]

and if the file contains more than 1024 chars nothing happens, at all??

[jbrea]

and if the file contains more than 1024 chars nothing happens, at all??

Exactly.

[kovidgoyal]

Sorry, I am out of ideas. You will need to look into running kitty from source and debugging.

[kovidgoyal]

The code for the send-text command is in send_text.py and the code that actually sends the data is in remote_control.py. Oh one thing, are you using --listen-on to run remote control with a socket?

[jbrea]

I did not use --listen-on before, but I just tried.
Almost same behaviour: it works fine with files that have no more than 1024 characters, but doesn't show anything except the error write() to peer socket failed with error: Broken pipe otherwise.

[jbrea]

I'm not used to debugging python code, but I will try...

[kovidgoyal]

I can replicate the issue with using --listen-on but not without

[jbrea]

Ah, I had a KITTY_LISTEN_ON env variable set in the terminal where I ran kitty without the --listen-on argument. Without this env variable and without using a socket, everything works.

Thanks a lot for your help!!!

[Luflosi]

Did you see the fix above? Compile from source and try it out.