Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Stephane Chazelas <stephane.chazelas@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: Wildcard expansion can fail with nonprinting characters
Date: Sat, 28 Sep 2019 07:07:37 +0100
Lines: 23
Approved: bug-bash@gnu.org
Message-ID: <mailman.7.1569650866.2651.bug-bash@gnu.org>
References: <pnih84x47ql.fsf@bow.cs.hmc.edu> <20190928060737.5gmjdcjoiaxgv4co@chaz.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Cc: bug-bash@gnu.org
To: Geoff Kuenning <geoff@cs.hmc.edu>
Envelope-to: bug-bash@gnu.org
Content-Disposition: inline
In-Reply-To: <pnih84x47ql.fsf@bow.cs.hmc.edu>
User-Agent: NeoMutt/20171215
Precedence: list
Xref: csiph.com gnu.bash.bug:15435

2019-09-27 16:52:50 -0700, Geoff Kuenning:
[...]
> $ mkdir /tmp/test$'\361'dir
> $ touch /tmp/test�dir/foo
> $ ls /tmp/test�dir/f*
> /tmp/test?dir/foo
> $ x=/tmp/test�dir
> $ echo "$x" | cat -v
> /tmp/testM-qdir
> $ ls "$x"/f*
> ls: cannot access '/tmp/test'$'\361''dir/f*': No such file or directory
[...]

I can reproduce on Ubuntu 18.04  with bash 4.4 in UTF-8 locales
and some other but not all multi-byte character locales
(ja_JP.eucjp, but not zh_CN.gb18030 for instance).

I can't reproduce in 5.0.10. Presumably, the issue has been
fixed already.

-- 
Stephane