diff options
author | Peter Stephenson <pws@users.sourceforge.net> | 2008-04-17 10:23:45 +0000 |
---|---|---|
committer | Peter Stephenson <pws@users.sourceforge.net> | 2008-04-17 10:23:45 +0000 |
commit | 78ce07b49f08964eaa08d68eb8f6a5595bbcfbc6 (patch) | |
tree | 3691862ef272257a5ecaa16d1d11db815cbf12c4 /Etc | |
parent | 35cedab2187d9472792656d0c46fc5acca1f1558 (diff) | |
download | zsh-78ce07b49f08964eaa08d68eb8f6a5595bbcfbc6.tar.gz zsh-78ce07b49f08964eaa08d68eb8f6a5595bbcfbc6.tar.xz zsh-78ce07b49f08964eaa08d68eb8f6a5595bbcfbc6.zip |
24818: add HIST_FCNTL_LOCK.
unposted: update NEWS with new features
Diffstat (limited to 'Etc')
-rw-r--r-- | Etc/FAQ.yo | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo index 238afcd3c..62f1842f3 100644 --- a/Etc/FAQ.yo +++ b/Etc/FAQ.yo @@ -2046,7 +2046,8 @@ sect(How does zsh handle multibyte input and output?) 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), tt(rxvt-unicode), and the Unicode version of - xterm, tt(uxterm), are known to handle combining characters. + xterm, tt(xterm -u8) or the front-end 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 |