[Bug 210890] Re: egrep -o '^..' Doesn't Match Start of Line Correctly.

2008-07-27 Thread Jean-Baptiste Lallement
Fixed in Intrepid. Please see https://wiki.ubuntu.com/StableReleaseUpdates if you would like to pursue a fix in stable releases. Thanks for your help. ** Changed in: grep (Ubuntu) Status: Confirmed => Fix Released -- egrep -o '^..' Doesn't Match Start of Line Correctly. https://bugs.lau

[Bug 210890] Re: egrep -o '^..' Doesn't Match Start of Line Correctly.

2008-04-27 Thread Ralph Corderoy
** Also affects: grep via http://savannah.gnu.org/bugs/?11579 Importance: Unknown Status: Unknown -- egrep -o '^..' Doesn't Match Start of Line Correctly. https://bugs.launchpad.net/bugs/210890 You received this bug notification because you are a member of Ubuntu Bugs, which is subsc

[Bug 210890] Re: egrep -o '^..' Doesn't Match Start of Line Correctly.

2008-04-27 Thread Ralph Corderoy
The GNU grep folks know about this problem. It's their https://savannah.gnu.org/bugs/?11579 Based on this Changelog entry, http://cvs.savannah.gnu.org/viewvc/grep/ChangeLog?root=grep&r1=1.279&r2=1.280 it appears they've fixed it already. Revision 1.280 of Changelog was released in their v

[Bug 210890] Re: egrep -o '^..' Doesn't Match Start of Line Correctly.

2008-04-02 Thread Koen Beek
Confirmed this also happens with grep (egrep calls grep but simply add the -E option) end of line ($) seems to works correctly (even on file with multiple line): $ echo 0123456789 | grep -o '..$' 89 $ it looks to me like, grep, once it has matched with something, simply starts the "new line" w