Docs: Shorten cmd:ref

docs/source/using_yosys/more_scripting/selections.rst

@@ -9,7 +9,7 @@ The selection framework
 
 .. todo:: reduce overlap with :doc:`/getting_started/scripting_intro` select section
 
-The :cmd:ref:`select` command can be used to create a selection for subsequent
+The `select` command can be used to create a selection for subsequent
 commands. For example:
 
 .. code:: yoscrypt
@@ -17,7 +17,7 @@ commands. For example:
     select foobar         # select the module foobar
     delete                # delete selected objects
 
-Normally the :cmd:ref:`select` command overwrites a previous selection. The
+Normally the `select` command overwrites a previous selection. The
 commands :yoscrypt:`select -add` and :yoscrypt:`select -del` can be used to add
 or remove objects from the current selection.
 
@@ -26,16 +26,16 @@ default, which is a complete selection of everything in the current module.
 
 This selection framework can also be used directly in many other commands.
 Whenever a command has ``[selection]`` as last argument in its usage help, this
-means that it will use the engine behind the :cmd:ref:`select` command to
+means that it will use the engine behind the `select` command to
 evaluate additional arguments and use the resulting selection instead of the
-selection created by the last :cmd:ref:`select` command.
+selection created by the last `select` command.
 
-For example, the command :cmd:ref:`delete` will delete everything in the current
+For example, the command `delete` will delete everything in the current
 selection; while :yoscrypt:`delete foobar` will only delete the module foobar.
-If no :cmd:ref:`select` command has been made, then the "current selection" will
+If no `select` command has been made, then the "current selection" will
 be the whole design.
 
-.. note:: Many of the examples on this page make use of the :cmd:ref:`show` 
+.. note:: Many of the examples on this page make use of the `show` 
    command to visually demonstrate the effect of selections.  For a more 
    detailed look at this command, refer to :ref:`interactive_show`.
 
@@ -59,7 +59,7 @@ Module and design context
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Commands can be executed in *module/* or *design/* context. Until now, all
-commands have been executed in design context. The :cmd:ref:`cd` command can be
+commands have been executed in design context. The `cd` command can be
 used to switch to module context.
 
 In module context, all commands only effect the active module. Objects in the
@@ -101,7 +101,7 @@ Operations on selections
 Combining selections
 ^^^^^^^^^^^^^^^^^^^^
 
-The :cmd:ref:`select` command is actually much more powerful than it might seem
+The `select` command is actually much more powerful than it might seem
 at first glance. When it is called with multiple arguments, each argument is
 evaluated and pushed separately on a stack. After all arguments have been
 processed it simply creates the union of all elements on the stack. So
@@ -190,7 +190,7 @@ Selecting logic cones
 :numref:`sumprod_01` shows what is called the ``input cone`` of ``sum``, i.e.
 all cells and signals that are used to generate the signal ``sum``. The ``%ci``
 action can be used to select the input cones of all object in the top selection
-in the stack maintained by the :cmd:ref:`select` command.
+in the stack maintained by the `select` command.
 
 As with the ``%x`` action, these commands broaden the selection by one "step".
 But this time the operation only works against the direction of data flow. That
@@ -222,9 +222,9 @@ The following sequence of diagrams demonstrates this step-wise expansion:
 Notice the subtle difference between :yoscrypt:`show prod %ci` and
 :yoscrypt:`show prod %ci %ci`.  Both images show the `$mul` cell driven by
 some inputs ``$3_Y`` and ``c``.  However it is not until the second image,
-having called ``%ci`` the second time, that :cmd:ref:`show` is able to
+having called ``%ci`` the second time, that `show` is able to
 distinguish between ``$3_Y`` being a wire and ``c`` being an input.  We can see
-this better with the :cmd:ref:`dump` command instead:
+this better with the `dump` command instead:
 
 .. literalinclude:: /code_examples/selections/sumprod.out
    :language: RTLIL
@@ -276,7 +276,7 @@ look at the first section:
 This loads :numref:`memdemo_src` and synthesizes the included module. Note that
 this code can be copied and run directly in a Yosys command line session,
 provided :file:`memdemo.v` is in the same directory. We can now change to the
-``memdemo`` module with ``cd memdemo``, and call :cmd:ref:`show` to see the
+``memdemo`` module with ``cd memdemo``, and call `show` to see the
 diagram in :numref:`memdemo_00`.
 
 .. figure:: /_images/code_examples/selections/memdemo_00.*
@@ -387,14 +387,14 @@ Storing and recalling selections
 The current selection can be stored in memory with the command ``select -set
 <name>``. It can later be recalled using ``select @<name>``. In fact, the
 ``@<name>`` expression pushes the stored selection on the stack maintained by
-the :cmd:ref:`select` command. So for example :yoscrypt:`select @foo @bar %i`
+the `select` command. So for example :yoscrypt:`select @foo @bar %i`
 will select the intersection between the stored selections ``foo`` and ``bar``.
 
 In larger investigation efforts it is highly recommended to maintain a script
 that sets up relevant selections, so they can easily be recalled, for example
 when Yosys needs to be re-run after a design or source code change.
 
-The :cmd:ref:`history` command can be used to list all recent interactive
+The `history` command can be used to list all recent interactive
 commands. This feature can be useful for creating such a script from the
 commands used in an interactive session.