about summary refs log tree commit diff
path: root/README
diff options
context:
space:
mode:
authorPeter Stephenson <pws@users.sourceforge.net>2006-09-15 13:17:27 +0000
committerPeter Stephenson <pws@users.sourceforge.net>2006-09-15 13:17:27 +0000
commitbb3628e898331edcd82da5d6291ef7c8812be267 (patch)
tree0064194df81c61ab42da6558a228085c4640c9f9 /README
parenta82ac460c29f18ee5e9d57322d977d0b93c0265f (diff)
downloadzsh-bb3628e898331edcd82da5d6291ef7c8812be267.tar.gz
zsh-bb3628e898331edcd82da5d6291ef7c8812be267.tar.xz
zsh-bb3628e898331edcd82da5d6291ef7c8812be267.zip
assume width 1 for control characters;
don't crash if width of repeated padding string is 0
Diffstat (limited to 'README')
-rw-r--r--README7
1 files changed, 7 insertions, 0 deletions
diff --git a/README b/README
index 88b6be3a9..78fcf5489 100644
--- a/README
+++ b/README
@@ -49,6 +49,13 @@ 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.
 
+The MULTIBYTE option is on by default where it is available; this
+causes many operations to recognise characters as in the current locale.
+Older versions of the shell always assumed a character was one byte.
+In some places the width of the character will be used; this is transparent
+when used for calculations of screen position, but also occurs, for
+example, in calculations of padding width.
+
 Zsh has previously been lax about whether it allows octets with the
 top bit set to be part of a shell identifier.  Older versions of the shell
 assumed all such octets were allowed in identifiers, however the POSIX