Configuration option to define wether to follows GNU sed's behaviour

or the posix standard.
Put the cleanup code back the way it was.

1 files changed, 13 insertions, 0 deletions

diff --git a/editors/Config.in b/editors/Config.in
index 14b698f..bced12c 100644
--- a/editors/Config.in
+++ b/editors/Config.in
@@ -42,6 +42,19 @@ config CONFIG_FEATURE_SED_EMBEDED_NEWLINE
 	  It works by translating '\n' to "\n" and back.
 	  It may introduce unexpected results if you use "\n" in your text.
 
+config CONFIG_FEATURE_SED_GNU_COMPATABILITY
+	bool " Behave consistent with GNU sed"
+	default y
+	depends on CONFIG_SED
+	help
+	  Where GNU sed doesnt follow the posix standard, do as GNU sed does.
+	  Current difference are in
+	    - N command with odd number of lines (see GNU sed info page)
+	    - Blanks before substitution flags eg.
+	        GNU sed interprets 's/a/b/ g' as 's/a/b/g'
+		Standard says 's/a/b/ g' should be 's/a/b/;g'
+	    - GNU sed allows blanks between a '!' and the function.
+
 config CONFIG_VI
 	bool "vi"
 	default n