docs: Fix remaining references

Fixes #5775.
This commit is contained in:
Fabian Homborg 2019-03-31 11:32:40 +02:00
parent e2cf10dd4f
commit 127c0e9764
9 changed files with 9 additions and 8 deletions

View file

@ -12,7 +12,7 @@ fish [OPTIONS] [-c command] [FILE [ARGUMENTS...]]
Description Description
----------- -----------
``fish`` is a command-line shell written mainly with interactive use in mind. The full manual is available <a href='index.html'>in HTML</a> by using the :ref:`help <cmd-help>` command from inside fish. ``fish`` is a command-line shell written mainly with interactive use in mind. The :ref:`full manual <intro>` is available in HTML by using the :ref:`help <cmd-help>` command from inside fish.
The following options are available: The following options are available:

View file

@ -14,4 +14,4 @@ Description
``funcsave`` saves the current definition of a function to a file in the fish configuration directory. This function will be automatically loaded by current and future fish sessions. This can be useful if you have interactively created a new function and wish to save it for later use. ``funcsave`` saves the current definition of a function to a file in the fish configuration directory. This function will be automatically loaded by current and future fish sessions. This can be useful if you have interactively created a new function and wish to save it for later use.
Note that because fish loads functions on-demand, saved functions will not function as <a href="index.html#event">event handlers</a> until they are run or sourced otherwise. To activate an event handler for every new shell, add the function to your <a href="index.html#initialization">shell initialization file</a> instead of using ``funcsave``. Note that because fish loads functions on-demand, saved functions will not function as :ref:`event handlers <event>` until they are run or sourced otherwise. To activate an event handler for every new shell, add the function to your :ref:`shell initialization file <initialization>` instead of using ``funcsave``.

View file

@ -19,7 +19,7 @@ Description
You can use :ref:`and <cmd-and>` or :ref:`or <cmd-or>` in the condition. See the second example below. You can use :ref:`and <cmd-and>` or :ref:`or <cmd-or>` in the condition. See the second example below.
The exit status of the last foreground command to exit can always be accessed using the <a href="index.html#variables-status">$status</a> variable. The exit status of the last foreground command to exit can always be accessed using the :ref:`$status <variables-status>` variable.
Example Example
------- -------

View file

@ -17,7 +17,7 @@ Description
``or`` statements may be used as part of the condition in an :ref:`and <cmd-if>` or :ref:`while <cmd-while>` block. See the documentation ``or`` statements may be used as part of the condition in an :ref:`and <cmd-if>` or :ref:`while <cmd-while>` block. See the documentation
for :ref:`if <cmd-if>` and :ref:`while <cmd-while>` for examples. for :ref:`if <cmd-if>` and :ref:`while <cmd-while>` for examples.
``or`` does not change the current exit status itself, but the command it runs most likely will. The exit status of the last foreground command to exit can always be accessed using the <a href="index.html#variables-status">$status</a> variable. ``or`` does not change the current exit status itself, but the command it runs most likely will. The exit status of the last foreground command to exit can always be accessed using the :ref:`$status <variables-status>` variable.
Example Example
------- -------

View file

@ -18,7 +18,7 @@ set ( -S | --show ) [SCOPE_OPTIONS] [VARIABLE_NAME]...
Description Description
----------- -----------
``set`` manipulates <a href="index.html#variables">shell variables</a>. ``set`` manipulates :ref:`shell variables <variables>`.
If set is called with no arguments, the names and values of all shell variables are printed in sorted order. If some of the scope or export flags have been given, only the variables matching the specified scope are printed. If set is called with no arguments, the names and values of all shell variables are printed in sorted order. If some of the scope or export flags have been given, only the variables matching the specified scope are printed.

View file

@ -189,7 +189,7 @@ which is logically equivalent to the following:
Standards Standards
--------- ---------
``test`` implements a subset of the <a href="http://www.unix.com/man-page/POSIX/1/test/">IEEE Std 1003.1-2008 (POSIX.1) standard</a>. The following exceptions apply: ``test`` implements a subset of the `IEEE Std 1003.1-2008 (POSIX.1) standard <http://www.unix.com/man-page/POSIX/1/test/>`__. The following exceptions apply:
- The ``<`` and ``>`` operators for comparing strings are not implemented. - The ``<`` and ``>`` operators for comparing strings are not implemented.

View file

@ -12,7 +12,7 @@ trap [OPTIONS] [[ARG] REASON ... ]
Description Description
----------- -----------
``trap`` is a wrapper around the fish event delivery framework. It exists for backwards compatibility with POSIX shells. For other uses, it is recommended to define an <a href='index.html#event'>event handler</a>. ``trap`` is a wrapper around the fish event delivery framework. It exists for backwards compatibility with POSIX shells. For other uses, it is recommended to define an :ref:`event handler <event>`.
The following parameters are available: The following parameters are available:

View file

@ -1,4 +1,5 @@
.. highlight:: fish .. highlight:: fish
.. _intro:
Introduction Introduction
============ ============

View file

@ -696,4 +696,4 @@ with ``/bin/bash``, ``/bin/tcsh`` or ``/bin/zsh`` as appropriate in the steps ab
Ready for more? Ready for more?
--------------- ---------------
If you want to learn more about fish, there is <a href="index.html">lots of detailed documentation</a>, an <a href="https://lists.sourceforge.net/lists/listinfo/fish-users">official mailing list</a>, the IRC channel \#fish on ``irc.oftc.net``, and the <a href="https://github.com/fish-shell/fish-shell/">github page</a>. If you want to learn more about fish, there is :ref:`lots of detailed documentation <intro>`, an `official mailing list <https://lists.sourceforge.net/lists/listinfo/fish-users>`__, the IRC channel \#fish on ``irc.oftc.net``, and the `github page <https://github.com/fish-shell/fish-shell/>`__.