On 10/13/11 16:51, Bruno Haible wrote: > But it does not help for the NeXTstep case, where sed chokes on any > regex delimiter that is not a slash. So what's the point?
Sorry, I didn't know that NeXTstep's sed was that badly
broken. The original message mentions only \|...|{...}
as not working, and my (as it turns out, vain) hope
was that bypassing the "{" would work around the problem.
