mirror of
https://github.com/kovidgoyal/kitty
synced 2026-07-10 14:14:48 +02:00
Finish remote control via socket implementation
This commit is contained in:
13
kitty/cli.py
13
kitty/cli.py
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user