From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: multibyte FAQ
Date: Fri, 16 Dec 2005 17:13:24 +0000 [thread overview]
Message-ID: <1051216171324.ZM10570@candle.brasslantern.com> (raw)
In-Reply-To: <20051216093949.GC21510@lorien.comfychair.org>
On Dec 16, 1:39am, Danek Duvall wrote:
}
} > The disadvantage is that you can't input multibyte characters via
} > the keyboard if they begin with the same meta sequence unless you
} > bind the more specific sequence starting with that byte
}
} Is there a simple way to find out which meta sequence block which
} multibyte characters for people who aren't too familiar with UTF-8
} encoding?
No, not really. The set of multibyte characters depends on the current
locale setting, and there are potentially thousands of them, most of
which will be broken by "bindkey -m".
} It might also be worth mentioning that, depending on your terminal
} emulator, you might be able to sidestep the problem entirely.
It's not *exactly* sidestepping the problem, because you still have to
avoid running "bindkey -m". It may be an alternative to "bindkey -m".
} In xterm at least, you can control whether the meta key sets the
} eighth bit or sends an escape character depending on the values of the
} eightBitInput and metaSendsEscape resources.
That doesn't have the desired effect for me, because eightBitInput has
to be false, which AFAICT means you can't send multibyte characters
either. Am I doing something wrong, or is my xterm version too old?
next prev parent reply other threads:[~2005-12-16 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 18:31 Peter Stephenson
2005-12-14 18:41 ` Peter Stephenson
2005-12-15 14:42 ` Peter Stephenson
2005-12-14 19:25 ` [22076] " Danek Duvall
2005-12-14 21:09 ` Peter Stephenson
2005-12-16 9:39 ` Danek Duvall
2005-12-16 17:13 ` Bart Schaefer [this message]
2005-12-18 19:38 ` Danek Duvall
2005-12-18 21:10 ` Bart Schaefer
2005-12-18 14:14 ` PATCH: multibyte FAQ (MacOS X) Jun T.
2005-12-18 15:26 ` Andrey Borzenkov
2005-12-19 9:08 ` Jun T.
2005-12-18 19:41 ` Peter Stephenson
2005-12-21 16:15 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1051216171324.ZM10570@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).