Clean up docs for --copy-env
This commit is contained in:
parent
f6cc0302c4
commit
b571c20acc
@ -81,11 +81,11 @@ currently active window.
|
|||||||
--copy-env
|
--copy-env
|
||||||
type=bool-set
|
type=bool-set
|
||||||
Copy the environment variables from the currently active window into the
|
Copy the environment variables from the currently active window into the
|
||||||
newly launched child process. It will not copy environment variables that have
|
newly launched child process. Note that most shells only set environment
|
||||||
been :code:`export`ed since the :code:`export` command does not change the environment
|
variables for child processes, so this will only copy the environment
|
||||||
of the shell, only of child processes launched in the shell. You can use remote control
|
variables that the shell process itself has not the environment variables
|
||||||
instead to have the current environment copied (:code:`allow_remote_control` must be on):
|
child processes inside the shell see. To copy that enviroment, use the
|
||||||
:code:`map kitty_mod+x remote_control launch --copy-env vim`.
|
kitty remote control feature with :code:`kitty @launch --copy-env`.
|
||||||
|
|
||||||
|
|
||||||
--location
|
--location
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user