From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Printf builtin missing v flag support
Date: Fri, 1 Jan 2016 23:12:32 +0100 [thread overview]
Message-ID: <CAKc7PVDsXof4TFRvtY15qThTEPqLz6NiSeL6dsKxqGXyK2aVeg@mail.gmail.com> (raw)
In-Reply-To: <160101135224.ZM10746@torch.brasslantern.com>
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
next prev parent reply other threads:[~2016-01-01 22:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <etPan.5684d3d1.74f2df6b.31ec@Ganymede>
2015-12-31 7:16 ` Starms, William Albert (MU-Student)
2015-12-31 10:44 ` Peter Stephenson
2015-12-31 18:48 ` Bart Schaefer
2016-01-01 21:26 ` Sebastian Gniazdowski
2016-01-01 21:35 ` Sebastian Gniazdowski
2016-01-01 21:52 ` Bart Schaefer
2016-01-01 22:12 ` Sebastian Gniazdowski [this message]
2016-01-02 4:17 ` Bart Schaefer
2016-01-02 7:17 ` Sebastian Gniazdowski
2016-01-02 21:42 ` Bart Schaefer
2016-01-02 21:54 ` Bart Schaefer
2016-01-04 5:50 ` Jun T.
2016-01-04 19:22 ` Bart Schaefer
2016-01-01 21:57 ` Eric Cook
2016-01-01 22:14 ` Eric Cook
2015-12-31 13:55 ` Eric Cook
2015-12-31 14:05 ` Eric Cook
2016-01-01 18:45 ` Stephane Chazelas
2016-01-01 21:17 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKc7PVDsXof4TFRvtY15qThTEPqLz6NiSeL6dsKxqGXyK2aVeg@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).