Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <160101135224.ZM10746@torch.brasslantern.com>
References: <068ca8f5-315b-444c-b281-5f183e1daa8c@email.android.com>
 <151231104858.ZM24513@torch.brasslantern.com> <CAKc7PVCXaicToQHdgaqnOmoqHjqQLxUXQSUrBx=fjs9JH2USKQ@mail.gmail.com>
 <160101135224.ZM10746@torch.brasslantern.com>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Fri, 1 Jan 2016 23:12:32 +0100
Message-ID: <CAKc7PVDsXof4TFRvtY15qThTEPqLz6NiSeL6dsKxqGXyK2aVeg@mail.gmail.com>
Subject: Re: Printf builtin missing v flag support
To: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

On 1 January 2016 at 22:52, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Jan 1, 10:26pm, Sebastian Gniazdowski wrote:
> }
> } Will this work for -x and -X?
>
> No, it doesn't.  It's mainly for "printf -v ..."; I only enabled it
> for plain "print" as an afterthought.  "print -v" joins the literal
> arguments into a string and stores that in the variable.
>
> To make it work with -x, -X, -C, etc. would require moving the memstream
> code to the top of the function, plus some related fiddling around later.

Could you implement that? The move of memstream code seems like a
cleanup, print would have full control of whether do memstream or not.

Best regards,
Sebastian Gniazdowski