Advertise the ability to run remote control scripts without turning on remote control

docs/changelog.rst

@@ -46,14 +46,14 @@ Detailed list of changes
 0.31.0 [future]
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+- Allow :ref:`easily running arbitrarily complex remote control scripts <rc_mapping>` without needing to turn on remote control (:iss:`6712`)
+
 - A new option :opt:`menu_map` that allows adding entries to the global menubar on macOS (:disc:`6680`)
 
 - A new :doc:`escape code <pointer-shapes>` that can be used by programs running in the terminal to change the shape of the mouse pointer (:iss:`6711`)
 
 - A new mouse action ``mouse_selection word_and_line_from_point`` to select the current word under the mouse cursor and extend to end of line (:pull:`6663`)
 
-- Allow :option:`kitty @ launch --allow-remote-control` to work even with background processes, by using a dedicated socketpair for the process (:iss:`6712`)
-
 - Allow using the full range of standard mouse cursor shapes when customizing the mouse cursor
 
 - macOS: When running the default shell with the login program fix :file:`~/.hushlogin` not being respected when opening windows not in the home directory (:iss:`6689`)

docs/remote-control.rst

@@ -282,6 +282,13 @@ are matched::
 
     map f1 remote_control !focus-window --match XXXXXX
 
+If you wish to run a more complex script, you can use::
+
+    map f1 launch --type=background --allow-remote-control /path/to/myscript
+
+In this script you can use the ``kitten @`` command to run as many remote
+control commands as you like.
+
 .. 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
    remote control infrastructure via keybings.