Why is allow_remote_control needed for Kitty integration?

[ayorgo]

I've tried it without and everything works just fine.

I couldn't find any reference to unix:@mykitty (or any other) socket in the codebase.

[mrjones2014]

This may be a holdover from a previous implementation that now uses a native Kitty feature.

I couldn't find any reference to unix:@mykitty (or any other) socket in the codebase.

Well mykitty is just a random example socket name, it can be anything. But did you look in the docs? It's right here: https://sw.kovidgoyal.net/kitty/remote-control/#remote-control-via-a-socket

[mrjones2014]

Can any other Kitty users confirm that remote control is no longer needed?

[ayorgo]

Yeah, I've seen unix:@mykitty mentioned as a dummy example in the Kitty docs and that made me wonder how this feature should be configured for the plugin.

So I looked up anything socket related in the codebase but found nothing so I disabled the feature in my Kitty config, restarted the terminal, and the plugin continued to work without change.

[mrjones2014]

based on the docs it sounds like it is needed in order for the plugin to issue shell commands to control the Kitty terminal.

https://sw.kovidgoyal.net/kitty/remote-control/

Are you using Kitty's built-in multiplexer? If not then you wouldn't need remote control. It's only needed for controlling Kitty's multiplexer through shell commands. If you're using a different multiplexer or none at all then it isn't needed.

[ayorgo]

Ah, sorry, not everything works as expected, actually. The navigation within Nvim itself has stopped working after I removed the listen_on parameter from Kitty's config.

When allow_remote_control feature is configured, Kitty sets the KITTY_LISTEN_ON environment variable to whatever socket was specified in listen_on. The env var is then accessed by the plugin code.