Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh 4.3.0-dev-2
- X-seq: zsh-users 9774
- From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- To: Zsh Users <zsh-users@xxxxxxxxxx>
- Subject: Re: zsh 4.3.0-dev-2
- Date: Sat, 10 Dec 2005 16:27:09 +0000
- In-reply-to: <200512101603.jBAG3Y5F006182@xxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <Pine.OSX.4.58.0512091947140.17953@xxxxxxxxxxxxxxx> <200512101603.jBAG3Y5F006182@xxxxxxxxxxxxxxxxx>
On Sat, 10 Dec 2005 16:03:33 +0000
Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx> wrote:
> If your keyboard provides such characters, don't use the "bindkey -m"
> option, which treats the high bit in 8-bit characters as if it were an
> escape character. A shell with multibyte enabled will warn if you set
> the option. You can remove all meta bindings with:
>
> bindkey -L | grep '\\M' |
> sed -e '/^bindkey \(-R \|\)"\\M/s/[^ ]*$/undefined-key/' |
> while read -r line; do eval $line; done
>
> (that's the simplest I could come up with; the shell doesn't provide a
> direct antidote), but that doesn't seem to undo the effect completely,
> so there may be a bug lurking.
It's because I didn't restore the self-insert binding. Add:
bindkey -R "\M-^@"-"\M-^?" self-insert
(although note this will override any meta bindings you have).
Messages sorted by:
Reverse Date,
Date,
Thread,
Author