[3.1.5] Bug report

[3.1.5] Bug report

[Marc Baudoin]

Hi,

I've upgraded from zsh 3.0.5 to try zsh 3.1.5 and I noticed two
problems.

The new zsh seems to have problems with files whose name contains
non ASCII characters:

skiff:~/tmp> cat généalogie 
zsh: command not found: alogie

The error message is quite weird...

Other problem, I've mapped the up and down arrows to the
up-line-or-search and down-line-or-search functions (which I find
quite useful):

bindkey '^[[B'  down-line-or-search
bindkey '^[[A'  up-line-or-search

but the arrow keys then don't work anymore.

These two problems doesn't exist in zsh 3.0.5.

-- 
Marc Baudoin   -=-   <babafou@babafou.eu.org>

Re: [3.1.5] Bug report

[Bart Schaefer]

On Nov 11,  3:23pm, Marc Baudoin wrote:
} Subject: [3.1.5] Bug report
}
} The new zsh seems to have problems with files whose name contains
} non ASCII characters:
} 
} skiff:~/tmp> cat généalogie 
} zsh: command not found: alogie

I can reproduce this in both the base 3.1.5 and in my own heavily-patched
copy (similar to the patched version PWS made available a few days ago).
I can confirm that it does not occur in an equivalently-configured 3.0.5.

} Other problem, I've mapped the up and down arrows to the
} up-line-or-search and down-line-or-search functions (which I find
} quite useful):
} 
} bindkey '^[[B'  down-line-or-search
} bindkey '^[[A'  up-line-or-search
} 
} but the arrow keys then don't work anymore.

This is fixed by the patch in zsh-workers/4476, which wasn't included
in the base 3.1.5, I presume because it also restores some other 3.0.5
behavior that the archive maintainer doesn't agree with.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com