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


Groups > gnu.bash.bug > #15800

Re: Filename Expansion bug

Path csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From Chet Ramey <chet.ramey@case.edu>
Newsgroups gnu.bash.bug
Subject Re: Filename Expansion bug
Date Mon, 13 Jan 2020 09:11:51 -0500
Lines 21
Approved bug-bash@gnu.org
Message-ID <mailman.2484.1578924719.1979.bug-bash@gnu.org> (permalink)
References <CAJV=ESGhY7Wu==vMeUS+icoLBYkONBxuUpTdoUsm3fv=EZFiEQ@mail.gmail.com> <66b2510f-a2cf-b4d3-4574-9193a9bc89c4@case.edu> <CAJV=ESHn1G2+9FSdtpTPT+CtqahNMiWJtRTE71PagS=H+2VA8A@mail.gmail.com> <8c2d195b-679c-08ca-cd01-2f4699995968@case.edu>
Reply-To chet.ramey@case.edu
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding 7bit
X-Trace usenet.stanford.edu 1578924720 18691 209.51.188.17 (13 Jan 2020 14:12:00 GMT)
X-Complaints-To action@cs.stanford.edu
Cc chet.ramey@case.edu, bug-bash@gnu.org
To Mickael KENIKSSI <k.mickael@gmail.com>
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1578924714; bh=aWpDFehGhIloaybOhnakEv9h4/bBZcrn7cO4ni7uSXE=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=7j1dJAAWTaFpm4tP7ZMe9NJFB+HAxABu4Fm3lQwEd4NGO25fnNg5tXm0JITaUV+U4X 9EyqAgnna4GocbPZ3XpptnJaTb92gsSdWAJ6Jci1naWGQvGFa56SBjtL0Z7pRWT5/R6 zhkfHuUIrZP6PNiOheKcMoskxamT2QWMJTFXL78rCGjrjjDOndjRtbCdJ9+rV96mQOz sYF0YQRIBaBuhYAgFIPTdy1jVxoA32OdCZv6oyQAzaaEVNUzSsIPT0q9addfacgfp9a UxXPVLSNUFKiLFMRLAnuZ5uOzM21zR2lujO0rKcgN8S4uoe2mDqvtVmErXqNBXpEaz7 6UO6egiQ==
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1578924712; bh=ry++H6c22xskvFhb9/HY02QOm0qlhAkzubFqJUsfZTA=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=fv/jk2r80YAZ1YLXTuulPguCDHDdmuvOALwIjE5XAAc/j19diJG34AHmIWdX+lR8T0 7Zf7OlLUFiPPfw8n39qQ5COS7kpw4pDGb+oQ8l5yiOXPmh0EpLsrlHqV1ke6i3x2NKg Num+WZRr1B80R7iZdgCcVy+at8rWkO8ttxc9wMy3yz6ZGve70l72wtRvx5+klfezcAZ GD33sXb5dhqzdtbXqv587CMKqw8lUJ9Y5CW5e/O9Y1HMzIEGdZzESTmOX98b9EDV+cx 4I4B1NavzeZ04pg0cCytu6PvcUPwh9uBuPGmmH1aj98WuRHA9Ic7YRFRSIYXAjuxhZl Ztc5Tl/Q==
User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
In-Reply-To <CAJV=ESHn1G2+9FSdtpTPT+CtqahNMiWJtRTE71PagS=H+2VA8A@mail.gmail.com>
Content-Language en-US
X-Junkmail-Status score=8/90, host=mpv4-2015.case.edu
X-Junkmail-PrAS-Raw score=8/90, refid=2.7.2:2020.1.13.133317:17:8.317, ip=, rules=DKIM_SIGNATURE, __HAS_REPLYTO, __HAS_CC_HDR, __MULTIPLE_RCPTS_CC_X2, __SUBJ_REPLY, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __TO_MALFORMED_2, __TO_NAME, __TO_NAME_DIFF_FROM_ACC, __HAS_REFERENCES, __REFERENCES, __HAS_FROM, FROM_EDU_TLD, __HAS_MSGID, __SANE_MSGID, DATE_TZ_NA, __USER_AGENT, __MOZILLA_USER_AGENT, __MIME_VERSION, __IN_REP_TO, __CT, __CT_TEXT_PLAIN, __CTE, __REPLYTO_SAMEAS_FROM_ADDY, __REPLYTO_SAMEAS_FROM_ACC, __FROM_DOMAIN_IN_ANY_CC2, __REPLYTO_SAMEAS_FROM_DOMAIN, __DKIM_ALIGNS_1, __DKIM_ALIGNS_2, __ANY_URI, __URI_MAILTO, __URI_WITH_PATH, __URI_NO_WWW, __CP_URI_IN_BODY, __SUBJ_ALPHA_NEGATE, __URI_IN_BODY, __URI_NOT_IMG, __MAIL_CHAIN, __FORWARDED_MSG, __BODY_NO_MAILTO, __NO_HTML_TAG_RAW, BODY_SIZE_700_799, BODYTEXTP_SIZE_3000_LESS, __MIME_TEXT_P1, __MIME_TEXT_ONLY, __URI_NS, HTML_00_01, HTML_00_10, [TRUNCATED], so=2010-03-03 19:42:08, dmn=2016-08-03-0138
X-detected-operating-system by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] [fuzzy]
X-Received-From 129.22.103.195
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 <8c2d195b-679c-08ca-cd01-2f4699995968@case.edu>
X-Mailman-Original-References <CAJV=ESGhY7Wu==vMeUS+icoLBYkONBxuUpTdoUsm3fv=EZFiEQ@mail.gmail.com> <66b2510f-a2cf-b4d3-4574-9193a9bc89c4@case.edu> <CAJV=ESHn1G2+9FSdtpTPT+CtqahNMiWJtRTE71PagS=H+2VA8A@mail.gmail.com>
Xref csiph.com gnu.bash.bug:15800

Show key headers only | View raw


On 1/9/20 6:09 AM, Mickael KENIKSSI wrote:
> Thanks for your comment.
> 
> I understand this may not sound of primary importance for you since they 
> are canonically equivalent, but sometimes what we really all care about is 
> the path as a literal string (be it well- or ill-formed), and not the 
> filesystem object it points to.

Pathname expansion deals with that filesystem object, and those filesystem
objects have a single slash as the directory separator. That's how the
bash implementation deals with it.

> I suppose it all comes down to an implementation question.

Indeed, it does.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

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


Thread

Re: Filename Expansion bug Chet Ramey <chet.ramey@case.edu> - 2020-01-13 09:11 -0500

csiph-web