From 7b477ccca8d6aac769ba9c25b2ca1e2d364bf7d2 Mon Sep 17 00:00:00 2001 From: Kovid Goyal Date: Mon, 17 Jun 2024 09:27:40 +0530 Subject: [PATCH] clarify some docs further --- kitty/options/definition.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kitty/options/definition.py b/kitty/options/definition.py index 3a54d1130..07ce50001 100644 --- a/kitty/options/definition.py +++ b/kitty/options/definition.py @@ -2920,9 +2920,9 @@ doesn't work, kitty will cycle through various known editors (:program:`vim`, opt('close_on_child_death', 'no', option_type='to_bool', ctype='bool', long_text=''' -Close the window when the child process (shell) exits. With the default value +Close the window when the child process (usually the shell) exits. With the default value :code:`no`, the terminal will remain open when the child exits as long as there -are still processes outputting to the terminal (for example disowned or +are still other processes outputting to the terminal (for example disowned or backgrounded processes). When enabled with :code:`yes`, the window will close as soon as the child process exits. Note that setting it to :code:`yes` means that any background processes still using the terminal can fail silently because