Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: Eli Schwartz Newsgroups: gnu.bash.bug Subject: Re: unquoted expansion not working (was Re: Not missing, but very hard to see) Date: Sun, 15 Dec 2019 13:46:10 -0500 Lines: 113 Approved: bug-bash@gnu.org Message-ID: References: <662e2328-f331-c554-afcf-fd3819f6beab@case.edu> <20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de> <5b5064a8-7175-42e7-1eb5-6374dee6c11e@redhat.com> <21761e28-c496-ff67-d7b7-628c9325085f@iki.fi> <9dd3a388-39b1-c059-de99-813f1e411764@case.edu> <5DF2987E.5000309@tlinx.org> <568aeaaa-22b3-c7b9-0e18-a92bef6d2ffb@iki.fi> <5DF2FE31.9070406@tlinx.org> <0ff3a920-94c2-b0c9-5631-0964955657aa@archlinux.org> <5DF3D78B.4090208@tlinx.org> <20191213184213.GO851@eeg.ccf.org> <5DF4BDF0.6000402@tlinx.org> <4b43ad78-75f6-f848-3d15-81cf7b400b36@archlinux.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ONK5ZV9JuIcmhTWSQ4KgYHVIU02xVYdjZ" X-Trace: usenet.stanford.edu 1576435590 30191 209.51.188.17 (15 Dec 2019 18:46:30 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=archlinux.org; s=orion; t=1576435575; bh=cTd2LOrrjjUr63ovmRfOTNFENglNqJD59oD6yNPeqlw=; h=Subject:To:References:From:Date:In-Reply-To; b=WZdqnqxnyKJ5qeYMgTypcGH0ct7IBBm2c89ENZuyGSjI52XRWPGqXDWvhkEIdFkYI U4hyhqommAR/bK9t9T8ueU77lV3u+s39CXzXpIfQaYfl+8qOvRn2i2UAImf0PVPX+v EQBde2iORlkp1yDMexN7B0Lvootp7JJqreFR1suzE+4ksAuPoafpi+uznGcWXfMY5/ YerRHfbZTyCEYVyeQhW9ZBNZlNXlv2FDIfAsZBf1VQ7eOR3dlMmvCBfjzGrk05b1cT KZLpMV5ZvuiwRgpw4akRfkprPmp3d9k7NzBAOGuikb+Z09BJI/AzBUfOokM+I/2KjK wgBeRv+xzd5+zJyCmXcSbpa01sS8l4Wg8AqQ9SHSwoJTJTBV3fE0sJFytG+Ln0aoax 9YehGfBlWOGgHhruUQKN/qOraIX2uqcaKCN3OX0Z2Udi0Aue1EDa5pGj6nGE2wPB6l XghgasfoB+upsunLl9JrdIpOPbz9Wy4plBYNXHS5hjGJX5UOIvXnwwn5MLwYp4lfXt EXv2Zb0sikODotT5GGwVwXTj3xp9P3ovi/7OqKbeHxUw6QgdLIjk0dIxusuwQbobL4 VXN985/tnoHA6z7qsIFLTuhoRrCez1WngZT5h5q664LMLbcTTT5ng7o57bRZvavvkm 7hFgk4dZ7fSwGhRBYURgJ7kM= X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 In-Reply-To: <5DF4BDF0.6000402@tlinx.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a01:4f8:160:6087::1 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <4b43ad78-75f6-f848-3d15-81cf7b400b36@archlinux.org> X-Mailman-Original-References: <662e2328-f331-c554-afcf-fd3819f6beab@case.edu> <20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de> <5b5064a8-7175-42e7-1eb5-6374dee6c11e@redhat.com> <21761e28-c496-ff67-d7b7-628c9325085f@iki.fi> <9dd3a388-39b1-c059-de99-813f1e411764@case.edu> <5DF2987E.5000309@tlinx.org> <568aeaaa-22b3-c7b9-0e18-a92bef6d2ffb@iki.fi> <5DF2FE31.9070406@tlinx.org> <0ff3a920-94c2-b0c9-5631-0964955657aa@archlinux.org> <5DF3D78B.4090208@tlinx.org> <20191213184213.GO851@eeg.ccf.org> <5DF4BDF0.6000402@tlinx.org> Xref: csiph.com gnu.bash.bug:15736 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ONK5ZV9JuIcmhTWSQ4KgYHVIU02xVYdjZ Content-Type: multipart/mixed; boundary="MGAAW4oN4HfVLProFhbXuPf8AZhQzB9DH" --MGAAW4oN4HfVLProFhbXuPf8AZhQzB9DH Content-Type: text/plain; charset=utf-8 Content-Language: en-US-large Content-Transfer-Encoding: quoted-printable On 12/14/19 5:48 AM, L A Walsh wrote: >> If on the other hand Chet decides that the man page's wording is not >> accurate, then the issue about whether to quote punctuation characters= >> becomes irrelevant.=C2=A0 The generation of punctuation characters is = an >> unexpected consequence, and the answer is Don't Do That. >> =C2=A0=20 > ----- > =C2=A0=C2=A0 No -- you don't go backwards -- it could break existing sc= ripts that > use that That's a ridiculous argument, essentially saying bash must retain bug-level compatibility with every previous version of every behavior. https://xkcd.com/1172/ But it's also beside the point, because I don't actually see anyone making the argument you're opposing. The proposal is to update the man page to declare the current behavior as "expected", and possibly include a note "abusing brace expansion to produce characters other than ASCII letters is fragile and results in non-intuitive behavior. Users are advised to not do it". The alternative, changing bash's behavior to make the output of my strings which happen to resemble brace expansion, suddenly produce an array of expanded characters, is "breaking my script what are you doing even stop making bash behave differently from version to version why don't you even comprehend backwards compatibility ARGHHHHHHHHHHHH". See, I can play the "people do unexpected things, don't break backwards compatibility" absurdity game too. > for one, but two -- are you going to limit it only to every > range of letters and numbers in unicode?=C2=A0 It seems allowing it to = work > generally would be easier than trying to only have it work on the multi= ple > ranges of unicode -- which I'd point out is consistent with bash growin= g to > be able to use unicode (when it used to not be so), and most features > working with unicode. So this is actually not an unreasonable suggestion, I guess. Although I can't really imagine a practical use for it, whereas generally with other "works with unicode data" features, I can. > =C2=A0=C2=A0 May not happen overnight, but a fix to quote meta-chars an= d allow all > characters, including, _eventually_ 'null' embedded in strings, since t= hat > does happen in the MS world and in C++ where counts instead of zstrings= are > more frequently found, but I won't be holding my breath for that result= =2E Wait what. Are you actually serious? Because this looks like trolling. --=20 Eli Schwartz Arch Linux Bug Wrangler and Trusted User --MGAAW4oN4HfVLProFhbXuPf8AZhQzB9DH-- --ONK5ZV9JuIcmhTWSQ4KgYHVIU02xVYdjZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEvSewel70XCra9w4EhIGKaBmvSpsFAl32f3MACgkQhIGKaBmv SpuRQRAAo5dY0lY58qt7OP8QZlVNwtrEeNWMk67KpFoSED424BYyd5BVLaaRz0RD 3omcF5adKX1cxB/8cNa3D89lzJjbuq3TubsCqOOFfQ8YEW6fQn1UeugW1taM5DNV UWSvxDwORgsIsTN864yOgd8yW+tV+DCjcOEm6ekJdv8JKeaKLuO4+2C/10qus2Dn Uu+jPAQRXht4bkd3fCc169AdRZLnWs74YdvtJPCyNhlutBsp92INZTLQDwK/w3bV 4Wo/PitQjOIOpkoSUk5svGYngx6OgsJbEROiRNaFNfRdI4I5XWn8NHYQRbDud1g2 k19KZxngh3MR1lIsV10PH7SZkHKimGNtSGh0yB2lIsEqmwgMnvA2sVKi01SXMKJu NGT0B/suK18p3ZMZuEvp7oiCIYtbA670PrfMVDwnSTYbQIGTIEhb8bpqCZkwQAZe OmDXaRohJ8HbEJv9WSup5BtrjaP21IBDj+jWRhZch5Ax3vkt8tvWB0atmY4uJn1p 2KjyJNOmIcgcfIHcgQtCvzAaMxnxelWKGa+NkEl9DquofgK+pYpfFMcE10X27257 /uy5ZhTY6fIQwTwBv0iBUQF+S4sScadfpPvzbldA1HPrCPpX4Z72pofKHXl0v4lM WpC61Z32OIZ3izjvFPK1o+TfFrHGkDJrhHjluf5VYCiFUs5w1yGJAjMEAQEKAB0W IQRgQRMEwJ02YoNA7v/OsWfvtXIr1gUCXfZ/cwAKCRDOsWfvtXIr1lJDD/9HbgvA Ftc3ezs53ajEqw5A4JeyDczjRRo8l1gy7pgqFkmwG5VAKxiEESIrJhk2q4LgBwb3 5kx0Rp7RDdnMsVkk1Sm3xXB+x/E603gBANC/YNUyet18jsIzwUQe3lADZyPTsvqf f40lU5GUSNVOITfKJFFPLcxrigcby1ISUL2TOJpgCID4UVOfPKHJmH20TruBafmC TZvRtaBxU/Nug3M+ibts9y4LmARXN2vxJFPUgC97TuvvJMQlBxD52h/GAwzAVkiY 8kGCkotIabihMV5yRDuwGPpaR6qsLbosmTRJDk6UMli2ppDA4qQ6FaMRU4HLVL/G U9FNssJsCtRx6yBFrRSbdt7AAUq7oRxH5ohX13aWE+EY63pV9qu93CwcGTCnbCr0 IKy/OgaKO0YbkfGzrypg540rVFp8BIk/do4wjywtjPZJlTQsG6LRfziKNfFg2WFR 71XCPP4p6xZ5H1UhEmk4IniEu+LSJdfhbbRNwaVX+dA0gB3oQZc75xPvwiSbiRc8 0rF2cyS5f4woZRmSAlv+ZmnwD1Bym3H0ljpagKgquhWSMwUUz3620rNDcBqw3ohU FMvVWhs4cXmlnwp+rJv6aHAmmbP7D3kyTSuBUDV8N5R4DbeXw2FBcin83yfNVqWz HWibM9nw/3KsL2sneQWlOutWXcubzA3p7iyr9g== =4rUK -----END PGP SIGNATURE----- --ONK5ZV9JuIcmhTWSQ4KgYHVIU02xVYdjZ--