Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15435 > unrolled thread

Re: Wildcard expansion can fail with nonprinting characters

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

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

#15435 — Re: Wildcard expansion can fail with nonprinting characters

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

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web