From 2570b43e829ccfc0f199fe61aafc24b1bd3fc7b1 Mon Sep 17 00:00:00 2001
From: Glenn L McGrath <bug1@ihug.co.nz>
Date: Tue, 16 Sep 2003 05:25:43 +0000
Subject: Configuration option to define wether to follows GNU sed's behaviour
 or the posix standard. Put the cleanup code back the way it was.

---
 editors/Config.in | 13 +++++++++++++
 1 file changed, 13 insertions(+)

(limited to 'editors/Config.in')

diff --git a/editors/Config.in b/editors/Config.in
index 14b698f5d..bced12cb1 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
-- 
cgit v1.2.3