On Wed, 22 Oct 2014 21:57:14 +0200 Ingo Schwarze
wrote:
> > So the newline before the close-brace is required. Since the code
> > matches the spec, I think we should change the doc to match both of
> > them. Or is there some reason this extension is required?
>
> That would be the following pa
Hi,
Philip Guenther wrote on Wed, Oct 22, 2014 at 10:46:43AM -0700:
> That looks like a documentation bug to me. To quote the POSIX spec:
> --
> [2addr] {editing command
> editing command
> ...
> }
>
> Execute a list of sed editing commands only when the pattern space
> is selected. The
On Wed, 22 Oct 2014 10:46:43 -0700 Philip Guenther
wrote:
> On Wed, Oct 22, 2014 at 8:37 AM, Christopher Zimmermann
> wrote:
> > $ sed -e "{ y/o/u/ }"
> > sed: 1: "{ y/o/u/ }": extra text at the end of a transform command
> >
> > but this is allowed according to the manual:
> >
> > Function
On Wed, Oct 22, 2014 at 8:37 AM, Christopher Zimmermann
wrote:
> $ sed -e "{ y/o/u/ }"
> sed: 1: "{ y/o/u/ }": extra text at the end of a transform command
>
> but this is allowed according to the manual:
>
> Functions can be combined to form a function list, a list of sed
> functions se
Hi
$ sed -e "{ y/o/u/ }"
sed: 1: "{ y/o/u/ }": extra text at the end of a transform command
but this is allowed according to the manual:
Functions can be combined to form a function list, a list of sed
functions separated by newlines, as follows:
{ function
fun
