From df229dafa0dc123e5ce9434d6e6715d24d4d58a8 Mon Sep 17 00:00:00 2001 From: Kovid Goyal Date: Fri, 21 Jun 2024 06:17:32 +0530 Subject: [PATCH] Clarify docs that remote_control_script is a convenience wrapper for launch --- docs/remote-control.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/remote-control.rst b/docs/remote-control.rst index 0a2f122aa73..bdc84369728 100644 --- a/docs/remote-control.rst +++ b/docs/remote-control.rst @@ -287,10 +287,11 @@ If you wish to run a more complex script, you can use:: In this script you can use ``kitten @`` to run as many remote control commands as you like and process their output. -:ac:`remote_control_script` is really just an alias for the +:ac:`remote_control_script` is similar to the :ac:`launch` command with ``--type=background --allow-remote-control``. For more advanced usage, including fine grained permissions, setting -env vars, etc. see the docs for the :doc:`launch ` command. +env vars, command line interpolation, passing data to STDIN, etc. +the :doc:`launch ` command should be used. .. note:: You do not need :opt:`allow_remote_control` to use these mappings, as they are not actual remote programs, but are simply a way to reuse the