Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Questions about multibyte input with zsh
- X-seq: zsh-workers 22967
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Questions about multibyte input with zsh
- Date: Sun, 05 Nov 2006 11:08:00 -0800
- In-reply-to: <8F46F6B8-CB85-4F20-9279-DCC7CF76725D@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <8F46F6B8-CB85-4F20-9279-DCC7CF76725D@xxxxxxx>
On Nov 4, 7:17pm, Jordan Breeding wrote:
}
} zsh 4.3.x: multibyte support is much improved in general, but I can't
} seem to get the OS X native input method to work, I can only use
} insert-composed-character
My guess would be that the native-input characters are not bound to
anything in ZLE when multibyte is enabled, and zsh is seeing them as
mutli-character sequences rather than as a single multibyte character.
Try adding a few "bindkey -s" commands to bind some of the native-input
byte sequences to insert-composed-character keystroke-sequences.
If that works, we may eventually be able to add something similar to
"bindkey -m" to set up those bindings automatically.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author