mirror of
https://github.com/fish-shell/fish-shell
synced 2024-12-26 12:53:13 +00:00
Add explanation to csh versus sh variable naming in docs.
darcs-hash:20080108194127-75c98-b44c6f18607cf270fae16179cd0df3e84f980b91.gz
This commit is contained in:
parent
71c2cde390
commit
30cfa2a445
1 changed files with 7 additions and 0 deletions
|
@ -931,6 +931,13 @@ values of most of these variables.
|
|||
- \c status, which is the exit status of the last foreground job to exit.
|
||||
- \c USER, which is the username. This variable can only be changed by the root user.
|
||||
|
||||
The names of these variables are mostly derived from the csh family of
|
||||
shells and differ from the ones used by Bourne style shells such as
|
||||
bash. The csh names where chosen because Bourne style names, such as
|
||||
?, * and @ lead to significantly less readable code, and much larger
|
||||
discoverability problems, and given the existence of tab completion,
|
||||
the keystroke savings are minimal.
|
||||
|
||||
Variables whose name are in uppercase are exported to the commands
|
||||
started by fish, those in lowercase are not exported. This rule is not
|
||||
enforced by fish, but it is good coding practice to use casing to
|
||||
|
|
Loading…
Reference in a new issue