Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        bh=jwYdTxrj9q6ku7B7HN3xNpawGZ1TyePeEXOqyWJYxy4=;
        b=pDhV094GreSNPJbiA2GleLdxgACeaChUz0ymnXk2k/TazHmab+OJu5tEfjEQCs8u1d
         O5DyXRagljdmd6l/T9ZoljL64r6w9GXWyZsrqC9a0BdkPH3NpkhB8k9FsGIimj1lJsIr
         DJSyShm5ww2gR0hnswO9Rk8ct9gYxoELI/Xpx3WHdHU1nKh2xFUGh8rdfFr4F3heEA7D
         JE3J9TtHydlrV7M8VXfO/JtF41dx5QsxthaCHpyLGO4rZhYO8WH83hQkfAdFjtL4sFB0
         XxGUqJxJE047rTY/EG3XpiaS++PkTg1GZ3GdCJ6hUGSXrmHPWsXxYAsBdE1vFbzJoyN2
         ojNA==
X-Received: by 10.112.13.99 with SMTP id g3mr19169651lbc.86.1451683616511;
 Fri, 01 Jan 2016 13:26:56 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <151231104858.ZM24513@torch.brasslantern.com>
References: <068ca8f5-315b-444c-b281-5f183e1daa8c@email.android.com> <151231104858.ZM24513@torch.brasslantern.com>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Fri, 1 Jan 2016 22:26:37 +0100
Message-ID: <CAKc7PVCXaicToQHdgaqnOmoqHjqQLxUXQSUrBx=fjs9JH2USKQ@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
Content-Transfer-Encoding: quoted-printable
X-Seq: zsh-workers 37476

On 31 December 2015 at 19:48, Bart Schaefer <schaefer@brasslantern.com> wro=
te:
> On Dec 31, 10:44am, Peter Stephenson wrote:
> }
> } The feature is obviously useful but the print implementation is
> } a nightmare of special cases making it hard to change without
> } considerable refactoring. That would probably be a Good Work, given
> } enough test cases to check it, but is going to have to wait for a
> } volunteer.
> }
> } I haven't checked whether -v is already in use in which case this is mo=
ot.
>
> -v is not in use, and the print implementation has already been refactore=
d
> to support the -z and -s options in printf, so this is actually rather
> easy.

Will this work for -x and -X? I requested earlier to make -X/x support
special outputs in order to avoid fork and you only mentioned what
would be needed to make this work. I was looking at printf
implementation and noticed many special cases and have chosen to
request the feature instead of implementing it. If now -x/X will work
with -v it will be great news to me because I will be able to quickly
expand tabs =E2=80=93 without a fork or plain Zsh code.

Best regards,
Sebastian Gniazdowski

