Re: Wildcard expansion can fail with nonprinting characters

From	Stephane Chazelas <stephane.chazelas@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Wildcard expansion can fail with nonprinting characters
Date	2019-09-28 07:07 +0100
Message-ID	<mailman.7.1569650866.2651.bug-bash@gnu.org> (permalink)
References	<pnih84x47ql.fsf@bow.cs.hmc.edu> <20190928060737.5gmjdcjoiaxgv4co@chaz.gmail.com>

Show all headers | View raw

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

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Wildcard expansion can fail with nonprinting characters Stephane Chazelas <stephane.chazelas@gmail.com> - 2019-09-28 07:07 +0100

csiph-web