Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: multibyte FAQ
- X-seq: zsh-workers 22088
- From: Danek Duvall <duvall@xxxxxxxxxxxxxx>
- To: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- Subject: Re: PATCH: multibyte FAQ
- Date: Fri, 16 Dec 2005 01:39:49 -0800
- Cc: Zsh hackers list <zsh-workers@xxxxxxxxxx>
- In-reply-to: <200512142109.jBEL9S5v003595@xxxxxxxxxxxxxxxxx>
- Mail-followup-to: Danek Duvall <duvall@xxxxxxxxxxxxxx>, Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>, Zsh hackers list <zsh-workers@xxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20051214192539.GE3640@xxxxxxxxxxxxxxxxxxxxx> <200512142109.jBEL9S5v003595@xxxxxxxxxxxxxxxxx>
On Wed, Dec 14, 2005 at 09:09:28PM +0000, Peter Stephenson 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?
It might also be worth mentioning that, depending on your terminal
emulator, you might be able to sidestep the problem entirely. 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. Other terminals may have similar setups. There
may still be a certain set of people who won't get exactly what they want,
but it's probably pretty small.
Anyway, thanks for the explanation!
Danek
Messages sorted by:
Reverse Date,
Date,
Thread,
Author