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

or the posix standard.
Put the cleanup code back the way it was.
This commit is contained in:
Glenn L McGrath
2003-09-16 05:25:43 +00:00
parent 204ff1cea4
commit 2570b43e82
5 changed files with 70 additions and 29 deletions

View File

@@ -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