Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: Dmitry Goncharov Newsgroups: gnu.bash.bug Subject: Re: Incorrect example for `[[` command. Date: Sat, 21 Sep 2019 14:55:09 -0400 Lines: 15 Sender: Dmitry Goncharov Approved: bug-bash@gnu.org Message-ID: References: <8e7c8ea4-2fdf-4809-0b50-ea1bfbbec165@case.edu> <20190921185509.GA5480@madrid> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1569092120 26188 209.51.188.17 (21 Sep 2019 18:55:20 GMT) X-Complaints-To: action@cs.stanford.edu Cc: hk , bug-bash@gnu.org To: Ilkka Virta Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=G1qo48ugG8XToh7jU1srMIQS+COCn+9brbcWvpvpO8w=; b=FQVOOkPC/NHLaR4H7B31j7blXRhstfLpMRSEClsYA+57oB5XE1201a6ItF6t/SVklN FbxteY5BM7VHwDwHlPBj2FbRI8iaX7KgNy51YJ3luIkk5VqKbcyqUThFuvhDBz8LVhu3 SG0Gy6e66eod1fWYRieYsbOVejQ4M/0Y4ma/FDPbkqtuumjEgHpQDIT35j0DF0GkgJ0t mj37wUsZBNMuPs+pxoQtEMddH5qdPKHxKo5R6nUTMd+JOBRHyM9P+ucQCudMgJ9AqrQj 6YpYJs2+2Qung3LAIRtb1Mb6Is4IfYi0Qedi0u4sKLU+iAL1/6hOcaXVT8sxDvie0r0S NrBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=G1qo48ugG8XToh7jU1srMIQS+COCn+9brbcWvpvpO8w=; b=aQfM/CazW9yMcdj9CPbrHGT+U79ynJzSK97ZawoPv7JRJxiTNS6o13iqq82BQZAl98 GRR0QmMWpMGinu3RB0T81NAd4lfLHVDLXUmfeGgePQxcK1netgDslNDwWCQoKSuKTwqX qH5Zko+MADIsLITSccoF04o+IywnP+inSdaBkv63k4Xm9NKiHEKqqMUkVcSGeyfS4qlw 0dyutKjLqEs75qd+MB+7u0Ntv9eCI01jUsmHUMHhB5RlquVCkqMM6j1tIj0QOEUc3/u4 /3w9LtZZ0c0/yoxB4cplQebmqS3aGUEdO5IPB2+M0jzGPOrDb3oOBf+zWAbgw2UEGs8A NGAQ== X-Gm-Message-State: APjAAAVKRHKY/yCVkUL0nNbX6fU0c+11SBky6PoRHl924Tw90fdIMVAP 2N1n6MGTZOfzof5theS04sY= X-Google-Smtp-Source: APXvYqwhAlU/Pz8ehR5MfkvqS9k+7I5O6NwhpAfZ9klD6o/tal2J3HfCKlM8EWiG+g0wfIrbZxYthw== X-Received: by 2002:ac8:3647:: with SMTP id n7mr9996162qtb.159.1569092109789; Sat, 21 Sep 2019 11:55:09 -0700 (PDT) Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::833 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: <20190921185509.GA5480@madrid> X-Mailman-Original-References: <8e7c8ea4-2fdf-4809-0b50-ea1bfbbec165@case.edu> Xref: csiph.com gnu.bash.bug:15395 On Sat, Sep 21, 2019 at 12:34:39PM +0300, Ilkka Virta wrote: > [[:space:]]*?(a)b isn't a well-defined POSIX ERE: > > 9.4.6 EREs Matching Multiple Characters > > The behavior of multiple adjacent duplication symbols ( '+', '*', '?', > and intervals) produces undefined results. > > https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/basedefs/V1_chap09.html This is unfortunate. *? and +? are widely used not greedy regexes. regards, Dmitry