Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Bug#419832: zsh: expanding non-ASCII filenames with <TAB>

X-seq: zsh-workers 23769
From: Peter Stephenson <pws@xxxxxxx>
To: zsh-workers@xxxxxxxxxx
Subject: Re: Bug#419832: zsh: expanding non-ASCII filenames with <TAB>
Date: Fri, 17 Aug 2007 15:22:10 +0100
Cc: Alan Curry <pacman@xxxxxxxxxxxx>, 419832-forwarded@xxxxxxxxxxxxxxx
In-reply-to: <20070817120844.GA9936@xxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
Organization: CSR
References: <20070817001222.GA19399@xxxxxxxxxxx> <200708170905.l7H9521T1534406@xxxxxxxxxxxxxxxxxxxx> <20070817120844.GA9936@xxxxxxxxxxx>

On Fri, 17 Aug 2007 08:08:44 -0400
Clint Adams <schizo@xxxxxxxxxx> wrote:
> There is apparently a bit of inconsistency here.  expand-or-complete and
> expand-word will eat the asterisk, but _expand_word won't.
> 
> What's worse is that if you `touch a b$'\300' c` in an empty directory,
> cat *<TAB> will only expand to "a b".

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 elements?

-- 
Peter Stephenson <pws@xxxxxxx>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070

.

Follow-Ups:
- Re: Bug#419832: zsh: expanding non-ASCII filenames with <TAB>
  - From: Clint Adams
- Re: Bug#419832: zsh: expanding non-ASCII filenames with <TAB>
  - From: Bart Schaefer

References:
- Re: Bug#419832: zsh: expanding non-ASCII filenames with <TAB>
  - From: Clint Adams

Messages sorted by: Reverse Date, Date, Thread, Author