You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The r,R,w,W commands parse the filename until end of the line. If whitespace, comments or semicolons are found, they will be included in the filename, leading to unexpected results.
Sedsed current matching for filenames:
# Regex patterns to identify special entitiespatt= {
#...'filename': r'[^\s]+', # _any_ not blank char (strange..)#...
}
There's a clear mismatch here. My code is wrong. Fix it.
The text was updated successfully, but these errors were encountered:
This is a syntax gotcha. From GNU sed documentation:
The r,R,w,W commands parse the filename until end of the line. If
whitespace, comments or semicolons are found, they will be included
in the filename, leading to unexpected results.
So adding that comment after the s///w flag was a mistake. It will
be considered part of the filename. This commit fixes the relevant
test cases.
From the html and token tests fixed in this commit, we can see
that sedsed actually consider that ending a real comment. Issue
#29 was opened to
fix sedsed code to correctly parse that.
From the GNU sed documentation:
Sedsed current matching for filenames:
There's a clear mismatch here. My code is wrong. Fix it.
The text was updated successfully, but these errors were encountered: