mirror of
https://github.com/fish-shell/fish-shell
synced 2024-11-11 15:37:24 +00:00
docs/tutorial: Remove some empty lines
[ci skip]
This commit is contained in:
parent
de3f862731
commit
a154384ff4
1 changed files with 0 additions and 12 deletions
|
@ -211,8 +211,6 @@ Variable substitution also occurs in double quotes, but not single quotes::
|
|||
|
||||
Unlike other shells, ``fish`` has no dedicated `VARIABLE=VALUE` syntax for setting variables. Instead it has an ordinary command: ``set``, which takes a variable name, and then its value.
|
||||
|
||||
|
||||
|
||||
::
|
||||
|
||||
>_ set name 'Mister Noodle'
|
||||
|
@ -358,7 +356,6 @@ Command substitutions are not expanded within quotes. Instead, you can temporari
|
|||
Unlike other shells, fish does not split command substitutions on any whitespace (like spaces or tabs), only newlines. This can be an issue with commands like ``pkg-config`` that print what is meant to be multiple arguments on a single line. To split it on spaces too, use ``string split``.
|
||||
|
||||
|
||||
|
||||
::
|
||||
|
||||
>_ printf '%s\n' (pkg-config --libs gio-2.0)
|
||||
|
@ -369,7 +366,6 @@ Unlike other shells, fish does not split command substitutions on any whitespace
|
|||
-lglib-2.0
|
||||
|
||||
|
||||
|
||||
Separating Commands (Semicolon)
|
||||
-------------------------------
|
||||
|
||||
|
@ -384,14 +380,12 @@ To write them on the same line, use the semicolon (";"). That means the followin
|
|||
echo chips
|
||||
|
||||
|
||||
|
||||
Exit Status
|
||||
-----------
|
||||
|
||||
Unlike other shells, ``fish`` stores the exit status of the last command in ``$status`` instead of ``$?``.
|
||||
|
||||
|
||||
|
||||
::
|
||||
|
||||
>_ false
|
||||
|
@ -423,14 +417,12 @@ As mentioned in `the section on the semicolon <#tut_semicolon>`__, this can also
|
|||
or echo "Backup failed"
|
||||
|
||||
|
||||
|
||||
Conditionals (If, Else, Switch)
|
||||
-------------------------------
|
||||
|
||||
Use ``if``, ``else if``, and ``else`` to conditionally execute code, based on the exit status of a command.
|
||||
|
||||
|
||||
|
||||
::
|
||||
|
||||
if grep fish /etc/shells
|
||||
|
@ -445,7 +437,6 @@ Use ``if``, ``else if``, and ``else`` to conditionally execute code, based on th
|
|||
To compare strings or numbers or check file properties (whether a file exists or is writeable and such), use :ref:`test <cmd-test>`, like
|
||||
|
||||
|
||||
|
||||
::
|
||||
|
||||
if test "$fish" = "flounder"
|
||||
|
@ -464,7 +455,6 @@ To compare strings or numbers or check file properties (whether a file exists or
|
|||
`Combiners <#tut_combiners>`__ can also be used to make more complex conditions, like
|
||||
|
||||
|
||||
|
||||
::
|
||||
|
||||
if grep fish /etc/shells; and command -sq fish
|
||||
|
@ -521,7 +511,6 @@ You can see the source for any function by passing its name to ``functions``::
|
|||
end
|
||||
|
||||
|
||||
|
||||
Loops
|
||||
-----
|
||||
|
||||
|
@ -550,7 +539,6 @@ Iterating over a list of numbers can be done with ``seq``::
|
|||
end
|
||||
|
||||
|
||||
|
||||
Prompt
|
||||
------
|
||||
|
||||
|
|
Loading…
Reference in a new issue