Finish remote control via socket implementation

This commit is contained in:
Kovid Goyal
2018-03-03 10:32:49 +05:30
parent ec989a45b5
commit 15f07f57bf
5 changed files with 85 additions and 47 deletions

View File

@@ -85,12 +85,13 @@ in the first |_ {appname}| instance within that group
--listen-on
Tell kitty to listen on the specified UNIX socket or TCP port for control
messages. For example, --listen-on=unix:/tmp/mykitty or
--listen-on=tcp:localhost:12345. On Linux systems, you can also use abstract
UNIX sockets, not associated with a file, like this: --listen-on=unix:@mykitty.
Note that this option will be ignored, unless you set allow_remote_control to yes
in kitty.conf
Tell kitty to listen on the specified address for control
messages. For example, |_ --listen-on=unix:/tmp/mykitty| or
|_ --listen-on=tcp:localhost:12345|. On Linux systems, you can also use abstract
UNIX sockets, not associated with a file, like this: |_ --listen-on=unix:@mykitty|.
To control kitty, you can send it commands with |_ kitty @| using the |_ --to| option
to specify this address. Note that this option will be ignored, unless you set
|_ allow_remote_control| to yes in |_ kitty.conf|
# Debugging options