diff --git a/doc_src/cmds/bind.rst b/doc_src/cmds/bind.rst index 20c1c7fd4..b51c02f79 100644 --- a/doc_src/cmds/bind.rst +++ b/doc_src/cmds/bind.rst @@ -31,7 +31,7 @@ To find out what sequence a key combination sends, you can use :ref:`fish_key_re ``COMMAND`` can be any fish command, but it can also be one of a set of special input functions. These include functions for moving the cursor, operating on the kill-ring, performing tab completion, etc. Use ``bind --function-names`` for a complete list of these input functions. -When ``COMMAND`` is a shellscript command, it is a good practice to put the actual code into a `function <#function>`__ and simply bind to the function name. This way it becomes significantly easier to test the function while editing, and the result is usually more readable as well. +When ``COMMAND`` is a shellscript command, it is a good practice to put the actual code into a :ref:`function ` and simply bind to the function name. This way it becomes significantly easier to test the function while editing, and the result is usually more readable as well. If a script produces output, it should finish by calling ``commandline -f repaint`` to tell fish that a repaint is in order.