Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: code completition / cannot delete characters
- X-seq: zsh-users 11259
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: code completition / cannot delete characters
- Date: Fri, 09 Mar 2007 08:13:54 -0800
- In-reply-to: <4916CF2F-0DA8-478B-96DC-B6154C90D98C@xxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <52211927-A3E8-4E51-8735-961A3BE83BB1@xxxxxxxxxxxxxxxxxx> <070309024427.ZM6023@xxxxxxxxxxxxxxxxxxxxxx> <4916CF2F-0DA8-478B-96DC-B6154C90D98C@xxxxxxxxxxxxxxxxxx>
On Mar 9, 3:29pm, Michael Worobcuk wrote:
}
} Hi Bart, thank you very mauchfor your response !
} >
} > What happens if you type: ESC x redisplay
} > (that is, the escape key, then x, then the word redisplay) and then
} > hit
} > the return key? Does that clean it up?
}
} I do not know that command sequence so I tried several times :)
}
} [hanno: /home/hanno]>splay
} zsh: command not found: splay
Hrm, something may be is messed up (or at least non-standard) with
your key bindings, because the two keys ESC x should have caused you
to get a new prompt like so:
[hanno: /home/hanno]>
execute:
At which point you would type "redisplay" and then hit return:
[hanno: /home/hanno]>
execute: redisplay
Instead it appears that the six keys ESC x r e d i are being swallowed
up as a single series. (This is the sort of thing that it's extremely
difficult to diagnose by email.)
} [hanno: /home/hanno]>r-screen
} zsh: command not found: r-screen
Hrm, part 2. Where did "r-screen" come from? Are you running zsh
inside a terminal multiplexer such as "screen"? Perhaps that is what
is eating some of the input keys.
} [hanno: /home/hanno]>echo $ZSH_VERSION
} 4.3.2
That's recent enough to have minimal multibyte support so the next
question is whether it's compiled in to your copy. When you run
the command
bindkey -m
do you get a warning about multibyte support being disabled?
} I should also mention that the german letters "ä" "ü" and "ö" are
} also not supported.
Have you tried using the insert-composed-char or insert-unicode-char
functions? You'll need to install them:
autoload -U insert-composed-char
zle -N insert-composed-char
and then bind them to a convenient key sequence with bindkey.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author