From 41cfe26898af5be1f2340edc8edbde6df1fe784b Mon Sep 17 00:00:00 2001 From: Alexis Bourget Date: Wed, 30 Sep 2020 20:31:04 +0200 Subject: [PATCH 1/3] use :code: block for @... in --stdin-source doc --- kitty/launch.py | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/kitty/launch.py b/kitty/launch.py index 54c655a55..84dbb7831 100644 --- a/kitty/launch.py +++ b/kitty/launch.py @@ -112,11 +112,11 @@ computers (for example, over ssh) or as other users. type=choices default=none choices=none,@selection,@screen,@screen_scrollback,@alternate,@alternate_scrollback -Pass the screen contents as :code:`STDIN` to the child process. @selection is -the currently selected text. @screen is the contents of the currently active -window. @screen_scrollback is the same as @screen, but includes the scrollback -buffer as well. @alternate is the secondary screen of the current active -window. For example if you run a full screen terminal application, the +Pass the screen contents as :code:`STDIN` to the child process. :code:`@selection` is +the currently selected text. :code:`@screen` is the contents of the currently active +window. :code:`@screen_scrollback` is the same as :code:`@screen`, but includes the +scrollback buffer as well. :code:`@alternate` is the secondary screen of the current +active window. For example if you run a full screen terminal application, the secondary screen will be the screen you return to when quitting the application. From 9742b0c5b1e847c286b64bad081c96a454b17c53 Mon Sep 17 00:00:00 2001 From: Alexis Bourget Date: Wed, 30 Sep 2020 20:31:35 +0200 Subject: [PATCH 2/3] Add docs precisions for launch and --copy-env --- kitty/launch.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/kitty/launch.py b/kitty/launch.py index 84dbb7831..97d26ad86 100644 --- a/kitty/launch.py +++ b/kitty/launch.py @@ -81,7 +81,10 @@ currently active window. --copy-env type=bool-set Copy the environment variables from the currently active window into the -newly launched child process. +newly launched child process. It will not copy environment variables that have +been :code:`export`ed since the :code:`export` command does not change the environment +of the shell, only of child processes launched in the shell. You can use remote control +instead to have the current environment copied. --location From 53468494394663c76e294d4007c4512f49802969 Mon Sep 17 00:00:00 2001 From: Alexis Bourget Date: Thu, 1 Oct 2020 00:56:35 +0200 Subject: [PATCH 3/3] Add example of remote_control use with launch --copy-env --- kitty/launch.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/kitty/launch.py b/kitty/launch.py index 97d26ad86..0220916c9 100644 --- a/kitty/launch.py +++ b/kitty/launch.py @@ -84,7 +84,8 @@ Copy the environment variables from the currently active window into the newly launched child process. It will not copy environment variables that have been :code:`export`ed since the :code:`export` command does not change the environment of the shell, only of child processes launched in the shell. You can use remote control -instead to have the current environment copied. +instead to have the current environment copied (:code:`allow_remote_control` must be on): +:code:`map kitty_mod+x remote_control launch --copy-env vim`. --location