Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~

Path	csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From	Paulo Marcel Coelho Aragão <marcelpaulo@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~
Date	Tue, 10 Jul 2018 12:07:13 -0300
Lines	15
Approved	bug-bash@gnu.org
Message-ID	<mailman.3380.1531235244.1292.bug-bash@gnu.org> (permalink)
References	<5b440fe8.1c69fb81.948f6.4d1e@mx.google.com> <20180710122718.wrrzjuqpmpns4o4o@eeg.ccf.org> <20180710130234.r5mwjc62adids7m5@monk> <69409432-a74c-a489-4d66-64a9f61cb9bf@case.edu>
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 1531235245 1241 208.118.235.17 (10 Jul 2018 15:07:25 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	bug-bash@gnu.org, bash@packages.debian.org
To	Chet Ramey <chet.ramey@case.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=vnMJ6COJP1+1Qi3cMrBaDxziLec3HYdjWUqZKeCZcsM=; b=TdCq3C9fjOwK+HBL5Dtp5o9e3d6jcIe3aamXW67X1DIiNt6Oe8Ym3ne/ukcFcWAxhP VLkEHWiGdRM8lJqER92D7CkVQ4C+reCKx22YhuxN22LpfMMKnziYCDZJcogjauUA2Xn2 g3aTPcgTM0SxvnSep7SsMyU4YZZn1fH02oZN3FCBlhInuftQsIZUGJEAny3/o0pAwRW9 +GhzukjgweCjFZQj4Ud60P/Yl7To8lZN3lAyFvMqR3PXrH2YIUWxpOW9vjHZJF9qm5Nt zADVZnq0nYI6ndl0COBToxwuu7SMjfnXOMQ0j2vyNJDAlkWz8TUfg6Kbm0u8cpehgk1+ Qafg==
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=vnMJ6COJP1+1Qi3cMrBaDxziLec3HYdjWUqZKeCZcsM=; b=RTgmhI2xfwqDXJXVjR2yKcrGchA9MMECJM3VfqIe72PyIdtWiFQ55CpHSkUjWfUyGk n1RFVhD0CyMz2v+9O8J2dkUFHjOLC9VQKPP6OineYg0BjaiLBiuPM0WrikO6ZkHBIOgc lInlSmT/nwlAXg1pPBpZytOomkRjiyn0uYchSV+AzTzU3Bcg3gnTKKl785IUrjXy7Khm beM92gJGGciG4KhVsRzcOxp0KLFDh8b1zcjhwl3R3m09pYgaGpGJ4bZ2IQhuDwGe7oqp SenVcZhu1tlrA8NsOCAmo+TksBjtR1SLZM7dj90fJKBkprvdLF+vNCHpnIE6m0NA/1fT YNKg==
X-Gm-Message-State	APt69E1HRxjyQFzAVwjfQ2uXoS5BKTdt2PqCS1Y5cu/NWfy6UyAcG3ep AiXdyYUcqJfsmXFCFUMqdrs=
X-Google-Smtp-Source	AAOMgpe9X8ewyNJFKBWat4Fev/DMynIyRgngw5VVhDRIPa5rMGzEAjZG+l8D9pUmI1NNKLZIYnSZWA==
X-Received	by 2002:aed:25cf:: with SMTP id y15-v6mr23616209qtc.341.1531235236515; Tue, 10 Jul 2018 08:07:16 -0700 (PDT)
Content-Disposition	inline
In-Reply-To	<69409432-a74c-a489-4d66-64a9f61cb9bf@case.edu>
User-Agent	NeoMutt/20171215
X-detected-operating-system	by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From	2607:f8b0:400d:c0d::22c
X-BeenThere	bug-bash@gnu.org
X-Mailman-Version	2.1.21
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	<http://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>
Xref	csiph.com gnu.bash.bug:14317

Show key headers only | View raw

On Tue, Jul 10, 2018 at 10:50:05AM -0400, Chet Ramey wrote:
>> […] However, this indicates to me that bash recognizes \< \> as word
>> anchors:
 
> No, it doesn't. It indicates that the system's POSIX regular expression
> implementation has extensions.

>> 3. bash evaluates them correctly when used with parameter expansion

> No. It passes them to the system's POSIX regexp library function, which
> understands them as an extension.

A subtle point, which makes sense. It really brings home what the reference
manual means by "as in regex3". Thanks for shedding light on this !

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

Thread

Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Paulo Marcel Coelho Aragão <marcelpaulo@gmail.com> - 2018-07-10 12:07 -0300

csiph-web