mirror of
https://github.com/fish-shell/fish-shell
synced 2024-12-27 05:13:10 +00:00
Minor documentation update
darcs-hash:20050924013157-ac50b-4ad9f6bb8da67a24999796a9a3de90e334645540.gz
This commit is contained in:
parent
5a7a14003f
commit
79b8ff535e
2 changed files with 13 additions and 8 deletions
|
@ -1252,15 +1252,16 @@ that even if a variable contains spaces, it will never be separated
|
||||||
into multiple arguments. If you want to tokenize a string, you can use
|
into multiple arguments. If you want to tokenize a string, you can use
|
||||||
the <a href="commands.html#tokenize">tokenize</a> command.
|
the <a href="commands.html#tokenize">tokenize</a> command.
|
||||||
|
|
||||||
Command substitution is specified using parenthesis.
|
Command substitution is specified using parenthesis, as in <tt>set name (whoami)</tt>.
|
||||||
|
|
||||||
There is no math mode, use bc.
|
There is no math mode, use bc.
|
||||||
|
|
||||||
The POSIX way of setting variables is <i>lame</i>. Whitespace
|
The POSIX way of setting variables is <i>lame</i>. Whitespace
|
||||||
sensitive languages are awful. "foo=bar" and "foo = bar" should not
|
sensitive languages are awful. "foo=bar" and "foo = bar" should not
|
||||||
mean different things? \c fish uses a builtin, <tt>set</tt> to set and
|
mean different things. \c fish uses a builtin, <tt>set</tt> to set and
|
||||||
remove environment variables. This keeps things consistent. In fish,
|
remove environment variables. While this may seem a bit obscure, this
|
||||||
everything, including the switch/case statement is a command.
|
makes for a very consistent language. In fish, everything, including
|
||||||
|
the loops, assignments and switch/case statements is a command.
|
||||||
|
|
||||||
In \c fish, all block types end with the \c end command.
|
In \c fish, all block types end with the \c end command.
|
||||||
|
|
||||||
|
|
|
@ -39,9 +39,13 @@ barrier_reply
|
||||||
</pre>
|
</pre>
|
||||||
|
|
||||||
A \c barrier command will result in a barrier_reply beeing added to
|
A \c barrier command will result in a barrier_reply beeing added to
|
||||||
the end of the senders queue. These commands are used to synchronize
|
the end of the senders queue of unsent messages. These commands are
|
||||||
clients.
|
used to synchronize clients, since once the reply for a barrier
|
||||||
|
message returns, the sender can know that any updates available at the
|
||||||
|
time the original barrier request was sent have been recieved.
|
||||||
|
|
||||||
\subecion fishd-files Files
|
\subsection fishd-files Files
|
||||||
|
|
||||||
~/.fishd.HOSTNAME permenent storage location for universal variale data
|
~/.fishd.HOSTNAME permenent storage location for universal variale
|
||||||
|
data. The data is stored as a set of \c set and \c set_export commands
|
||||||
|
such as would be parsed by fishd.
|
||||||
|
|
Loading…
Reference in a new issue