Comment # 5 on bug 1198463 from Christian Boltz

(In reply to Noel Power from comment #3)
> We discussed it here and decided that maybe a non printable delimiter is
> probably a better choice (and avoids mostly any chance that it could be part
> of a path name scanned by sed) so we chose the first single byte ascii char
> that worked e.g. 001

That's an interesting delimiter ;-) which I never used, and that might make the
script a bit more interesting to read. (And I won't even think about copy&paste
;-)

To make things a bit easier - the delimiter should be avoided (or escaped) in
the sed command (the 's/foo/bar/'), but it shouldn't be a problem if it appears
in the input data (in this case the path name). This also means using ';' as
delimiter (as my patch does) should work without problems.

If you want a quick confirmation of the above:
    echo 'test;delimiter' | sed 's;t;b;'