Make the primary use case for remote control via socket explicit
This commit is contained in:
parent
7722ba8b8a
commit
5004cf2dbf
1 changed files with 2 additions and 1 deletions
|
|
@ -108,7 +108,8 @@ simpler :option:`kitty --single-instance` option, see ``kitty --help`` for that.
|
|||
|
||||
Remote control via a socket
|
||||
--------------------------------
|
||||
First, start |kitty| as::
|
||||
To control kitty from outside kitty, it is necessary to setup a socket to
|
||||
communicate with kitty. First, start |kitty| as::
|
||||
|
||||
kitty -o allow_remote_control=yes --listen-on unix:/tmp/mykitty
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue