https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136
--- Comment #3 from Ed Maste <emaste at freebsd dot org> --- > the posix standard does not seem to disallow \n in the replacement string so > i think freebsd sed should be fixed (or report the bug to the austingroup). I can't find language that specifies sed must interpret escape sequences in the replacement string. Anyway, it does seem like it would be a useful thing for BSD sed to handle, but it's what we've got today. I also just confirmed that sed on OS X behaves the same way.
