grep - Bugs: bug #21401, Newline inserted by grep at EOF...
You are not allowed to post comments on this tracker with your current authentication level.
bug #21401: Newline inserted by grep at EOF causes false positives
Submitter: | None | ||
Submitted: | Tue 23 Oct 2007 01:57:24 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Invalid |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed |
Sat 06 Feb 2010 01:08:45 PM UTC, comment #1: |
Paolo Bonzini <bonzini> |
Tue 23 Oct 2007 01:57:24 PM UTC, original submission:
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-02-06 | bonzini | Status | None | Invalid | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-02a9.
Corresponding source code
grep operates by reading one line from the input stream, removing any trailing newline, and matching the pattern against it. The fact that grepping \x0a works is actually a bug in grep -P (in fact it doesn't work with grep/grep -E/grep -F).