From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24042 invoked from network); 19 Apr 2001 19:32:51 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 19 Apr 2001 19:32:51 -0000 Received: (qmail 18712 invoked by alias); 19 Apr 2001 19:32:45 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14045 Received: (qmail 18700 invoked from network); 19 Apr 2001 19:32:45 -0000 To: zsh-workers@sunsite.auc.dk (Zsh hackers list), Paul Falstad Subject: Re: problem with 8-bit characters In-reply-to: "Paul Falstad"'s message of "Thu, 19 Apr 2001 01:02:50 PDT." <10104190102.ZM9386@zoof.cts.com> Date: Thu, 19 Apr 2001 20:34:30 +0100 From: Peter Stephenson Message-Id: <20010419193430.E1E58139C3@pwstephenson.fsnet.co.uk> Paul Falstad wrote: > I would like to mention a bug that's been there since the beginning > (and has come back to haunt me). If you have a filename which > includes one of the character tokens (like 0x84) then zsh will > of course have lots of problems dealing with that file. > > example: > > zsh% ls Albumbl?tter' Op. 124.wav' = > > ls: Albumbl > tter Op. 124.wavv: No such file or directory > ^^^^ Are you sure this is still there? This was supposed to be fixed some time ago in both 3.0 and 3.1. I can't get this to happen now. -- Peter Stephenson Work: pws@csr.com Web: http://www.pwstephenson.fsnet.co.uk