[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #56823] -regextype egrep compatibility issue, requires full string
From: |
Isaac Freeman |
Subject: |
[bug #56823] -regextype egrep compatibility issue, requires full string match as opposed to egrep |
Date: |
Wed, 28 Aug 2019 16:40:58 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 |
URL:
<https://savannah.gnu.org/bugs/?56823>
Summary: -regextype egrep compatibility issue, requires full
string match as opposed to egrep
Project: findutils
Submitted by: memotype
Submitted on: Wed 28 Aug 2019 08:40:57 PM UTC
Category: find
Severity: 3 - Normal
Item Group: Wrong result
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.6.0
Fixed Release: None
_______________________________________________________
Details:
$ find -version
find (GNU findutils) 4.6.0.225-235f
...
Issue: Running this
find . -regextype egrep -regex '\.ya?ml$'
finds nothing, while
find . | egrep '\.ya?ml$'
finds everything fine. Meanwhile
find . -regextype egrep -regex '.*\.ya?ml$'
works fine. I understand that *find* usually only matches the whole string,
but it seems like it is misleading/confusing/unexpected that "-regextype
egrep" isn't copy-and-paste-compatible with actual *egrep*.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56823>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #56823] -regextype egrep compatibility issue, requires full string match as opposed to egrep,
Isaac Freeman <=