Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    You could narrow the problem down quickly by trying the sed commands one-at-a-time to see which one is generating the error. Also, after fixing it, it's generally not necessary to run a lot of sed commands in a row; just use sed -e 'edit1' -e 'edit2' -e 'edit3' ... or sed 'edit1; edit2; edit3; ... Commented Feb 4, 2020 at 8:23
  • Welcome to the site. If at all possible, copy-and-paste all console output like you already did for the first example. Also, please add information in what OS and sed` version you are using, there may be slight differences in (expected) behaviour depending on these circumstances. Commented Feb 4, 2020 at 8:51
  • This was on a virtual CentOS on VMware Horizon. The step before chaining all the commands together was to actually input them one by one and test them out. Which I had no problem doing. It was only when I had to do this chaining step that I got that error no matter what I tried. Also I did try to single-quote, and that did not work either. Commented Feb 4, 2020 at 19:04