From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@sunsite.dk, Jordan Breeding <jordan.breeding@mac.com>
Subject: Re: Questions about multibyte input with zsh
Date: Sun, 5 Nov 2006 22:55:02 +0000 [thread overview]
Message-ID: <20061105225502.a7bf5add.p.w.stephenson@ntlworld.com> (raw)
In-Reply-To: <061105110800.ZM26817@torch.brasslantern.com>
On Sun, 05 Nov 2006 11:08:00 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> 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.
This seems like a good guess... if you don't know what to do, try typing
"read<Return>" then hitting one of the sequences you want zsh to handle.
These should show up interpreted by the terminal (things like "^[[15~"
etc. etc.) These are the strings zsh will get. If you post these
together with the Unicode characters the sequences represent we might be
able to work out what's going on.
It may even be documented somewhere...
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
prev parent reply other threads:[~2006-11-05 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 1:17 Jordan Breeding
2006-11-05 19:08 ` Bart Schaefer
2006-11-05 22:55 ` Peter Stephenson [this message]
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=20061105225502.a7bf5add.p.w.stephenson@ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=jordan.breeding@mac.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).