Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160101131741.ZM10623@torch.brasslantern.com>
Date: Fri, 1 Jan 2016 13:17:41 -0800
In-Reply-To: <20160101184516.GB8456@chaz.gmail.com>
Comments: In reply to Stephane Chazelas <stephane.chazelas@gmail.com>
        "Re: Printf builtin missing v flag support" (Jan  1,  6:45pm)
References: <etPan.5684d3d1.74f2df6b.31ec@Ganymede> 
	<etPan.5684d62f.51cb8f6f.31ec@Ganymede> 
	<20160101184516.GB8456@chaz.gmail.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Printf builtin missing v flag support
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jan 1,  6:45pm, Stephane Chazelas wrote:
}
} ksh93 tries to only fork to execute external commands. For
} builtins when used in command substitutions, ksh93 just adds
} their output to the substituted value

If we identified early enough that the command was to be a builtin
(which I'm not sure we do) then the HAVE_OPEN_MEMSTREAM code from
bin_print() could be copied to somewhere in the getoutput() +
readoutput() flow.

Would probably require some other finagling in case we rely on the
fork for preservation of state.