|
From: | James Youngman |
Subject: | [bug #28237] strange behavior (maybe a bug, maybe not...) [needs better explanation of the problem] |
Date: | Sun, 15 Aug 2010 15:58:45 +0000 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.2 (KHTML, like Gecko) Chrome/5.0.342.7 Safari/533.2 |
Update of bug #28237 (project findutils): Status: Need Info => Invalid Assigned to: None => jay _______________________________________________________ Follow-up Comment #5: The first sentence of the description of the egrep regular expresison type says: @node egrep regular expression syntax @subsection @samp{egrep} regular expression syntax The character @samp{.} matches any single character except newline. Here the . just isn't matching the newline. You might want to try "-regextype posix-extended". ~/tmp/t$ find . -regextype posix-extended -regex '.*new.*' -print0 | od -c 0000000 . / n e w n l i n e 0000013 ~/tmp/t$ find . -regextype egrep -regex '.*new.*' -print0 | od -c 0000000 _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?28237> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |