mirror of
https://github.com/kovidgoyal/kitty
synced 2026-07-28 19:21:38 +02:00
Remove socket prewarming
The potential for breakage is too high, and I am working on an alternative solution that will be better long term. Prewarming is still used for kittens launched via keybindings
This commit is contained in:
@@ -142,17 +142,6 @@ Variables that kitty sets when running child programs
|
||||
A public key that programs can use to communicate securely with kitty using
|
||||
the remote control protocol. The format is: :code:`protocol:key data`.
|
||||
|
||||
.. envvar:: KITTY_PREWARM_SOCKET
|
||||
|
||||
Path to a UNIX domain socket used to avoid Python interpreter startup
|
||||
latency when running kittens, or remote control or using ``kitty +launch`` or
|
||||
``kitty +runpy``.
|
||||
|
||||
.. envvar:: KITTY_PREWARM_SOCKET_REAL_TTY
|
||||
|
||||
Path to the the PTY used to run the prewarmed process in when using
|
||||
:envvar:`KITTY_PREWARM_SOCKET`.
|
||||
|
||||
.. envvar:: WINDOWID
|
||||
|
||||
The id for the :term:`OS Window <os_window>` the program is running in. Only available
|
||||
|
||||
Reference in New Issue
Block a user