about summary refs log tree commit diff
path: root/README
diff options
context:
space:
mode:
authorPaul Ackersviller <packersv@users.sourceforge.net>2007-05-31 03:37:13 +0000
committerPaul Ackersviller <packersv@users.sourceforge.net>2007-05-31 03:37:13 +0000
commit602b1670bc3973cd6796f96916290dcef4ce2b73 (patch)
tree02f6e0d7b0e2ed1bad3846c8d788ad1e64f8043c /README
parentd9544f55dab0d825c59b9a4100ac2d97a9427569 (diff)
downloadzsh-602b1670bc3973cd6796f96916290dcef4ce2b73.tar.gz
zsh-602b1670bc3973cd6796f96916290dcef4ce2b73.tar.xz
zsh-602b1670bc3973cd6796f96916290dcef4ce2b73.zip
Merge of workers/{21790,22195,22198,22272,22305,22360,22365}.
Diffstat (limited to 'README')
-rw-r--r--README37
1 files changed, 33 insertions, 4 deletions
diff --git a/README b/README
index a345de32f..c027f94d6 100644
--- a/README
+++ b/README
@@ -26,11 +26,40 @@ 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 preceding.  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
 behaviour.
 
+The variable HOME is no longer set by the shell if zsh is emulating any
+other shell at startup; it must be present in the environment or set
+subsequently by the user.  It is valid for the variable to be unset.
+
+Zsh has previously been lax about whether it allows octets with the
+top bit set to be part of a shell identifier.  With --enable-multibyte set,
+this is now completely disabled.  This is a temporary fix until the main
+shell handles multibyte characters properly and the appropriate library
+tests can be used.  This change may be reviewed if no such permanent fix
+is forthcoming.
+
+The completion style pine-directory must now be set to use completion
+for PINE mailbox folders; previously it had the default ~/mail.  This
+change was necessary because otherwise recursive directories under
+~/mail were searched by default, which could be a considerable unnecessary
+hit for anyone not using PINE.  The previous default can be restored with:
+  zstyle ':completion:*' pine-directory ~/mail
+
 Documentation
 -------------
 
@@ -41,7 +70,7 @@ Doc/Zsh/*.yo	The master source for the zsh documentation is written in
 		It is not required by zsh but but it is a nice program so
 		you might want to get it anyway, especially if you are a
 		zsh developer.  It can be downloaded from
-		ftp://ftp.lilypond.org/pub/yodl/
+		ftp://yodl.sourceforge.net/
 
 Doc/zsh*.1	Man pages in nroff format.  These will be installed
 		by "make install.man" or "make install".  By default,
@@ -69,9 +98,9 @@ Doc/intro.ms	An introduction to zsh in troff format using the ms
 
 For more information, see the website, as described in the META-FAQ.
 
-If you do not have the necessary tools to process these documents,
-PostScript, ASCII, Info and DVI versions are available in the separate
-file zsh-doc.tar.gz at the archive sites listed in the META-FAQ.
+If you do not have the necessary tools to process these documents, PDF,
+Info and DVI versions are available in the separate file zsh-doc.tar.gz at
+the archive sites listed in the META-FAQ.
 
 The distribution also contains a Perl script in Utils/helpfiles which
 can be used to extract the descriptions of builtin commands from the