Permalink
Browse files

4.3.0-dev-3

  • Loading branch information...
1 parent 3e6fae8 commit 32f03e33e7976fced6e47befa9f3c9c11fc49e46 Peter Stephenson committed Feb 6, 2006
Showing with 14 additions and 4 deletions.
  1. +3 −0 ChangeLog
  2. +2 −2 Config/version.mk
  3. +2 −2 INSTALL
  4. +7 −0 README
View
@@ -1,5 +1,8 @@
2006-02-06 Peter Stephenson <pws@csr.com>
+ * 22196: INSTALL, README, Config/version.mk: developement
+ version 4.3.0-dev-3
+
* 22195: README, Src/init.c, Src/params.c, Src/subst.c,
Src/utils.c, Src/Modules/newuser.c: don't set HOME in the shell,
only if passed by the environment; handle the fallout.
View
@@ -27,5 +27,5 @@
# This must also serve as a shell script, so do not add spaces around the
# `=' signs.
-VERSION=4.3.0-dev-2
-VERSION_DATE='December 9, 2005'
+VERSION=4.3.0-dev-3
+VERSION_DATE='February 6, 2006'
View
@@ -282,8 +282,8 @@ and to work when configured with --enable-multibyte on:
- OS X 10.4.3 (problems have been reported with multibyte characters
in HFS file names)
- NetBSD 2.0.2
-
-Any help with Solaris 8 or 9 would be appreciated.
+ - Solaris 8+ (inputting multibyte characters from the keyboard doesn't
+ work in some installations).
The main shell is not yet aware of multibyte characters, so for example the
length of a scalar parameter will return the number of bytes, not
View
7 README
@@ -34,6 +34,13 @@ behaviour.
The variable HOME is no longer set by the shell; it must be present
in the environment. 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.
+
Documentation
-------------

0 comments on commit 32f03e3

Please sign in to comment.