grep - Bugs: bug #30455, \s now matches whitespace
You are not allowed to post comments on this tracker with your current authentication level.
bug #30455: \s now matches whitespace
Submitter: | None | ||
Submitted: | Thu 15 Jul 2010 08:34:59 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Fixed |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed |
Fri 16 Jul 2010 08:41:40 PM UTC, comment #1: |
Paolo Bonzini <bonzini> |
Thu 15 Jul 2010 08:34:59 PM UTC, original submission:
$ echo " " | grep -c '^\s'
|
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-07-16 | bonzini | Status | None | Fixed | |
Open/Closed | Open | Closed | |||
Summary | \\s now matches whitespace | \s now matches whitespace |
Powered by Savane 3.13-d3ae.
Corresponding source code
The escapes were already handled this way by the backtracking matcher. So the behavior was inconsistent depending on whether grep used the DFA matcher or the backtracking matcher.
I committed a documentation patch to document \s and \S.
Thank you for the bug report. This bug has been fixed in the
development sources, which can be downloaded using git from
git://git.sv.gnu.org/grep.git