jeff/chezmoi
1
0
Fork 0
Code Releases Activity

Update home/.config/kitty/advanced.conf

Browse Source
This commit is contained in:
Jeff Lance
2025-08-10 12:42:17 +02:00
parent d1ed515771
commit 00641e63d2
1 changed files with 18 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
home/dot_config/kitty/advanced.conf
View File

@@ -28,7 +28,7 @@ close_on_child_death no
#: to yes means that any background processes still using the terminal
#: can fail silently because their stdout/stderr/stdin no longer work.
allow_remote_control no
allow_remote_control yes
#: Allow other programs to control kitty. If you turn this on other
#: programs can control all aspects of kitty, including sending text
@@ -36,6 +36,23 @@ allow_remote_control no
#: content of windows, etc. Note that this even works over ssh
#: connections.
listen_on unix:/tmp/mykitty
#: Listen to the specified socket for remote control connections.
#: Note that this will apply to all kitty instances. It can be overridden
#: by the kitty --listen-on command line option.
#: For UNIX sockets, such as unix:${TEMP}/mykitty or unix:@mykitty (on Linux).
#: Environment variables are expanded and relative paths are resolved
#: with respect to the temporary directory. If {kitty_pid} is present,
#: then it is replaced by the PID of the kitty process, otherwise the PID
#: of the kitty process is appended to the value, with a hyphen.
#: For TCP sockets such as tcp:localhost:0 a random port is always used even
#: if a non-zero port number is specified.
#: See the help for kitty --listen-on for more details.
#: Note that this will be ignored unless allow_remote_control is set to either:
#: yes, socket or socket-only.
#: Changing this option by reloading the config is not supported.
# env
#: Specify environment variables to set in all child processes. Note