Re: [PATCH?] Nofork and removing newlines

[Oliver Kiddle <opk@xxxxxxx>]

Bart Schaefer wrote:
> like ${|REPLY=...} when of course piping to "read" etc. are also valid
> ways to assign to REPLY.  How often would there be a command name with
> no arguments in that position?

Probably not all that often.

> I hesitate in suggesting this, but ... is there any existing case in
> which "${{" is valid?  If not, I think I can change ${|var|...} to be
> ${{var}...} without too much violence (except to the doc, bleah).

Inner `$' in nested parameter expansions are fairly superfluous in
general. ${|var|...} is closer to the REPLY default with ${|...} but
other than that, I marginally prefer ${{var}...}
Certainly if it does involve much violence, what we currently have is
working.

> > That might look like a default value assignment to someone
>
> Would ${{=var}...} look better?  The doubled braces do give me pause.

Not as good as ${={var}...} but probably better.

> This is the code diff to make emulation trim all, ${ ... } trim one,
> "${ ... }" trim none ... not re-doing the doc diff yet.

Looks good to me.

Oliver