about summary refs log tree commit diff
path: root/Etc/FAQ.yo
diff options
context:
space:
mode:
authorPeter Stephenson <pws@users.sourceforge.net>2008-04-16 09:59:32 +0000
committerPeter Stephenson <pws@users.sourceforge.net>2008-04-16 09:59:32 +0000
commitbd79dd923832b364a5448554dafce7a22bac773a (patch)
treeaea70e6470c3b19e84b1f9bb310527c3bb92fd8f /Etc/FAQ.yo
parent1875c12734938595033715a948f50b05b76bca3d (diff)
downloadzsh-bd79dd923832b364a5448554dafce7a22bac773a.tar.gz
zsh-bd79dd923832b364a5448554dafce7a22bac773a.tar.xz
zsh-bd79dd923832b364a5448554dafce7a22bac773a.zip
24821: update notes in FAQ on combining characters,
fix up cursor on exit from user-defined widget
Diffstat (limited to 'Etc/FAQ.yo')
-rw-r--r--Etc/FAQ.yo5
1 files changed, 3 insertions, 2 deletions
diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
index 703bf02de..238afcd3c 100644
--- a/Etc/FAQ.yo
+++ b/Etc/FAQ.yo
@@ -2045,7 +2045,8 @@ sect(How does zsh handle multibyte input and output?)
   be displayed within the same screen area as the base character.  As not
   all terminals handle this, even if they correctly display the base
   multibyte character, this option is not on by default.  The KDE terminal
-  emulator tt(konsole) is known to handle combining characters.
+  emulator tt(konsole), tt(rxvt-unicode), and the Unicode version of
+  xterm, tt(uxterm), are known to handle combining characters.
 
   The tt(COMBINING_CHARS) option only affects output; combining characters
   may always be input, but when the option is off will be displayed
@@ -2157,7 +2158,7 @@ url(http://www.unicode.org/charts/)(http://www.unicode.org/charts/).
   however, using UTF-8 massively extends the number of valid characters
   that can be produced.
 
-  See also url(http://www.cl.cam.ac.uk/~mgk25/unicode.html#input)http://www.cl.cam.ac.uk/~mgk25/unicode.html#input)
+  See also url(http://www.cl.cam.ac.uk/~mgk25/unicode.html#input)(http://www.cl.cam.ac.uk/~mgk25/unicode.html#input)
   for general information on entering Unicode characters from a keyboard.