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


Groups > gnu.bash.bug > #15435

Re: Wildcard expansion can fail with nonprinting characters

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> (permalink)
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
X-Trace usenet.stanford.edu 1569650867 20206 209.51.188.17 (28 Sep 2019 06:07:47 GMT)
X-Complaints-To action@cs.stanford.edu
Cc bug-bash@gnu.org
To Geoff Kuenning <geoff@cs.hmc.edu>
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=m/AjsMUJZ0Qe1/BI3wwQUid8+TzSNuaJakrFJwKf9EE=; b=DLUn++g9fcF8eGlHhzvzRJbvo4XE7vv0LJDcL4NWJWhRCei5J4+vgUAai7RIcWliGu oiazU1r7Cvm/9cox3vh3wl8QyaMpmxWVzc6Pe2mF1IP7zAUNORX4WlZiARD0daZ1EaPt GtZrm2o9xikdNoYFw1L/d56UvUfGpihNI8Km5liEVSoOylE/1okJ/TKcYpbZL3TTzVq6 5dfY2JZM82LX245gVba6nLrpzHH1ZG8s5Oz7JRrys0js0TlXST0JLKFU5BTaxOBd3GVb 3qMFvkjJNw/zzb3FgfIT9ft8Our+MsZMaEirt9XISVPROmS6S/UAYeg3Fhy+ROwcxhuT Cy0g==
X-Google-DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=m/AjsMUJZ0Qe1/BI3wwQUid8+TzSNuaJakrFJwKf9EE=; b=DMWKYAGKq7R3pszlbGp5wwnqhK+aZx4RHg6pgTpvp8NciRp22A59dJOTRa6w28JklH XwAiixGIsFWuoebOaMnW7Je+eTAb48v+yV9PUbFJpDoL5mSpPyocb5XdRxfchkhh5l/C G72kQr3U9D7dMO66PnDf2IKPaDWxu7PXTWv8rcbTPHLF017HU/2LTb35mumv9/Rd/x6R itDIATsC7u439ctSPSuJ3HtRfDopIFtSdzr6LL+Vl0k3Hy/LPP8WB9/TFQnXHSwTDOGD joD2bmoh4G0Ywq5IGG/mwViO2bKstVVRdpG75D/jA407wHUewuICwfdPxSl1tvPxyvz6 JSLw==
X-Gm-Message-State APjAAAWNvYV3NNKZKkMdeo79QoxchnYZznpdnB9kCYvoxsppMwV8crij ukRwPbltXa2LyMsSO2O+/K4=
X-Google-Smtp-Source APXvYqz0v7qlnVIwupsOfX1tjUpdWdK/pp1+yyT2fI6JDLZzVw13FFy6/SKTV4XDuziLQqhvsPc6Tw==
X-Received by 2002:a1c:4d0d:: with SMTP id o13mr9990171wmh.19.1569650860977; Fri, 27 Sep 2019 23:07:40 -0700 (PDT)
Content-Disposition inline
In-Reply-To <pnih84x47ql.fsf@bow.cs.hmc.edu>
User-Agent NeoMutt/20171215
X-detected-operating-system by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From 2a00:1450:4864:20::331
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <20190928060737.5gmjdcjoiaxgv4co@chaz.gmail.com>
X-Mailman-Original-References <pnih84x47ql.fsf@bow.cs.hmc.edu>
Xref csiph.com gnu.bash.bug:15435

Show key headers only | 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