mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-09-08 12:01:21 +02:00
30780: document that set -o failures are hard but setopt failures are soft
This commit is contained in:
parent
ce658b3c3c
commit
7f767568a6
2 changed files with 11 additions and 1 deletions
|
@ -1,3 +1,8 @@
|
|||
2012-11-08 Peter Stephenson <pws@csr.com>
|
||||
|
||||
* 30780: Doc/Zsh/builds.yo: document that set -o failures are
|
||||
hard but setopt failures are soft.
|
||||
|
||||
2012-11-07 Oliver Kiddle <opk@zsh.org>
|
||||
|
||||
* Benjamin R. Haskell: 30737: Completion/Unix/Command/_git:
|
||||
|
@ -302,5 +307,5 @@
|
|||
|
||||
*****************************************************
|
||||
* This is used by the shell to define $ZSH_PATCHLEVEL
|
||||
* $Revision: 1.5753 $
|
||||
* $Revision: 1.5754 $
|
||||
*****************************************************
|
||||
|
|
|
@ -1361,6 +1361,11 @@ or without the tt(no) prefix remains the same in this case.
|
|||
If the tt(-m) flag is given the arguments are taken as patterns
|
||||
(which should be quoted to protect them from filename expansion), and all
|
||||
options with names matching these patterns are set.
|
||||
|
||||
Note that a bad option name does not cause execution of subsequent shell
|
||||
code to be aborted; this is behaviour is different from that of `tt(set
|
||||
-o)'. This is because tt(set) is regarded as a special builtin by the
|
||||
POSIX standard, but tt(setopt) is not.
|
||||
)
|
||||
findex(shift)
|
||||
cindex(parameters, positional)
|
||||
|
|
Loading…
Reference in a new issue