; one of the things i *really* dislike about gnu sed (the others are too
; far gone to be worth considering) is it doesn't support \123 style
; escapes
That's funny, the following seems to suggest GNU sed is one of the few
seds that DOES support it (which make IT not worth considering,
GNU extensions that don't work everywhere are responsible for a great
deal of evil I've seen in the world).
GNU sed v3.02.80
Now a,i,c commands can accept a string after them. Range syntax now
supports "/RE/,+n" (next n lines) or "/RE/,~n" (till the next line
which is a multiple of n). NULs permitted in regexes; \n, \t, \a,
\f, \xHH hex codes supported on LHS and RHS; more changes. An alpha
test release which (if found bug-free) will become GNU sed version
3.03. Supersedes GNU sed-3.02a.
; you have to end up doing evilness like:
; sed "s/`echo -ne '\000'`//g"
; which just gets annoying after a while..
certainly more annoying than using a more appropriate tool.
r.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
