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
Note that inside x.cmd_txt.text, there's a double \n when there should be only one.
In the x.sed file, the last line is foo\, which implies there will be a new line to the i command text. But there isn't. Note that for GNU sed, it works the same as if it was a normal foo in the last line:
$ seq 5 | sed -e '3i\' -e 'foo'12foo345
$ seq 5 | sed -e '3i\' -e 'foo\'12foo345
$
sedparse should not return that extra \n in this case.
The text was updated successfully, but these errors were encountered:
Note that inside
x.cmd_txt.text
, there's a double\n
when there should be only one.In the
x.sed
file, the last line isfoo\
, which implies there will be a new line to thei
command text. But there isn't. Note that for GNU sed, it works the same as if it was a normalfoo
in the last line:sedparse should not return that extra
\n
in this case.The text was updated successfully, but these errors were encountered: