Bug#295506: zsh: End-key changes case of several characters insted of going to eol

2005-02-18 Thread Clint Adams
> For me it is: > > aterm > [8~ end > [7~ home > > eterm > [8~ end > [7~ home > > Is it necessary to map those to the right keys for the > particular terminal? Yes, /etc/zsh/zshrc is using terminfo to do this. Do you get the following output in aterm and eterm? % bindkey | grep '\[[78]~'

Bug#295506: zsh: End-key changes case of several characters insted of going to eol]

2005-02-18 Thread Benjamin Peter
Hi Clint, thanks for your concern. On Thu, Feb 17, 2005 at 09:22:35PM -0500, Clint Adams wrote: > I'll change the /etc/zsh/zshrc to bind Insert to switch between insert > and overwrite mode. Sounds good. > Could you tell me what escape codes are being sent for Home and End in > aterm and Eterm?

Bug#295506: zsh: End-key changes case of several characters insted of going to eol

2005-02-17 Thread Clint Adams
> Independent from that the 'Insert'-key makes lower-case > characters to upper-case and vice versa. 'Insert' isn't bound to anything, and xterm sends ^[[2~ -- so it's switching to command mode, then transposing. I'll change the /etc/zsh/zshrc to bind Insert to switch between insert and overwrite

Bug#295506: zsh: End-key changes case of several characters insted of going to eol

2005-02-16 Thread Benjamin Peter
Package: zsh Version: 4.2.4-2 Severity: important Hi, I am not absolutely shure if the source of problem is zsh but since it is reproducable on several terminals and the problem doesn't exist with bash, I decided to tell you about it. I type e.g. 'gvim .trosmo' and use the Arrow keys to move bac