From d21735de2d7380d96cd42458c6d9775143abe6ea Mon Sep 17 00:00:00 2001 From: Matt Kraai Date: Wed, 2 Jan 2002 17:56:38 +0000 Subject: [PATCH] * editors/sed.c (parse_edit_command): Require a newline after the backslash after an edit command. * testsuite/sed/sed-requires-newline-after-edit-command: New. --- editors/sed.c | 2 +- testsuite/sed/sed-requires-newline-after-edit-command | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 testsuite/sed/sed-requires-newline-after-edit-command diff --git a/editors/sed.c b/editors/sed.c index fe1c0db..1c026d3 100644 --- a/editors/sed.c +++ b/editors/sed.c @@ -322,7 +322,7 @@ static int parse_edit_cmd(struct sed_cmd *sed_cmd, const char *editstr) * */ - if (editstr[1] != '\\' && (editstr[2] != '\n' || editstr[2] != '\r')) + if (editstr[1] != '\\' || (editstr[2] != '\n' && editstr[2] != '\r')) error_msg_and_die("bad format in edit expression"); /* store the edit line text */ diff --git a/testsuite/sed/sed-requires-newline-after-edit-command b/testsuite/sed/sed-requires-newline-after-edit-command new file mode 100644 index 0000000..37ebc66 --- /dev/null +++ b/testsuite/sed/sed-requires-newline-after-edit-command @@ -0,0 +1 @@ +! busybox sed -e 'i\foo'