diff options
| author | Peter Stephenson <pws@users.sourceforge.net> | 2006-02-16 14:28:53 +0000 |
|---|---|---|
| committer | Peter Stephenson <pws@users.sourceforge.net> | 2006-02-16 14:28:53 +0000 |
| commit | 5a6452742793d99bd899c50d3412db40275e6d9a (patch) | |
| tree | 9546ea07c0b876109a0854138163e5953732c3c6 /README | |
| parent | 5602319cb7508f998046453751bb69ffd9afeac7 (diff) | |
| download | zsh-5a6452742793d99bd899c50d3412db40275e6d9a.tar.gz zsh-5a6452742793d99bd899c50d3412db40275e6d9a.tar.xz zsh-5a6452742793d99bd899c50d3412db40275e6d9a.zip | |
22272: 4.3.0-dev-4 zsh-4.3.0-dev-4
Diffstat (limited to 'README')
| -rw-r--r-- | README | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/README b/README index 84a00706f..816c0819e 100644 --- a/README +++ b/README @@ -26,6 +26,17 @@ Possible incompatibilities Since 4.2: +The option SH_WORD_SPLIT, used in Bourne/Korn/Posix shell compatibility +mode, has been made more like other shells in the case of substitutions of +the form ${1+"$@"} (a common trick used to work around problems in older +Bourne shells) or any of the related forms with the + replaced by - or = +with an optional colon following. Previously, with SH_WORD_SPLIT in +effect, this expression would cause splitting on all white space in the +shell arguments. (This was always regarded as a bug but was long-standing +behaviour.) Now it is treated identically to "$@". The same change +applies to expressions with forced splitting such as ${=1+"$@"}, but +otherwise the case where SH_WORD_SPLIT is not set is unaffected. + The "unset" builtin now does not regard the unsetting of non-existent variables as an error, so can still return status 0 (depending on the handling of other arguments). This appears to be the standard shell |