Bug#419832: zsh: expanding non-ASCII filenames with

2007-08-18 Thread Alan Curry
Here's a backtrace showing where the extra characters get lost during an expand operation (touch a$'\300' and then cat a*) #0 stringaszleline (instr=0x100e0850 "cat a\300", incs=6, outll=0xfc97658, outsz=0xfc97890, outcs=0xfc97684) at zle_utils.c:244 #1 0x0fc70224 in unmetafy_line () at zle_

Bug#419832: zsh: expanding non-ASCII filenames with

2007-08-17 Thread Clint Adams
On Fri, Aug 17, 2007 at 03:22:10PM +0100, Peter Stephenson wrote: > I can believe there's some logic missing here, but it's not currently > clear to me here what. Could you post an explicit recipe for > getting from an unconfigured shell to an expansion that doesn't > (somehow) display all the ele

Bug#419832: zsh: expanding non-ASCII filenames with

2007-08-17 Thread Alan Curry
Clint Adams writes the following: > >On Wed, Apr 18, 2007 at 02:31:42AM -0400, Alan Curry wrote: >> In the following demonstration, the first keypress inserted the $'\300' >> for me. The second keypress, typed immediately after the asterisk, >> should expand the glob into $'\300' also, but instea

Bug#419832: zsh: expanding non-ASCII filenames with doesn't work

2007-08-16 Thread Clint Adams
On Wed, Apr 18, 2007 at 02:31:42AM -0400, Alan Curry wrote: > In the following demonstration, the first keypress inserted the $'\300' > for me. The second keypress, typed immediately after the asterisk, > should expand the glob into $'\300' also, but instead it just erases the > asterisk, replaci

Bug#419832: zsh: expanding non-ASCII filenames with doesn't work

2007-04-17 Thread Alan Curry
Package: zsh Version: 4.3.2-25 Severity: normal In the following demonstration, the first keypress inserted the $'\300' for me. The second keypress, typed immediately after the asterisk, should expand the glob into $'\300' also, but instead it just erases the asterisk, replacing it with nothing