zsh-users
 help / color / mirror / code / Atom feed
From: Ben Klein <robobenklein@gmail.com>
To: zsh-users@zsh.org
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>,
	Joey Pabalinas <joeypabalinas@gmail.com>
Subject: Re: Capturing STDOUT without subshells or file I/O
Date: Mon, 17 Sep 2018 16:13:19 -0400	[thread overview]
Message-ID: <cd8bc7e0-7ae1-8c94-8dea-9b529b2a8fb2@gmail.com> (raw)
In-Reply-To: <20180903184353.yzujt7ywnlvufeye@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1185 bytes --]

So I just rewrote a large portion of a codebase on being able to use
`printf -v`, but it looks like this support was added after ZSH 5.1,
which I intend to support. (Ubuntu 16.04 still has it.)

So I guess the question is up again, how should I capture the `printf`
output without the `-v` option, no subshells, and no file I/O? Is there
a different method for ZSH v5.1?

I would like to do `printf '%.2f' "3.4" | read var` but it appears that
the command before the pipe causes a subshell to be opened.

Or potentially, is there some way I can make a wrapper that will use
`printf -v` when available, but falls back to another method?


On 09/03/2018 02:43 PM, Joey Pabalinas wrote:
> On Mon, Sep 03, 2018 at 02:02:14PM +0000, Daniel Shahaf wrote:
>> Just pass -v to the builtin printf, e.g.,
>>
>> % printf -v foo 'a%03d' 42
>> % typeset -p foo
>> a042
>> % 
> Much nicer, wow. Looks like I'll be revising quite a few of my scripts
> today.
>

-- 
*\Ben Klein*
Founder and Owner of Robosane, robobenklein@robosane.net
You can find me elsewhere online as 'robobenklein'.
If you need to contact me securely, I am also reachable via GPG, or on
Keybase.

[-- Attachment #1.1.2: Type: text/html, Size: 1991 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2018-09-17 20:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 20:57 Ben Klein
2018-09-03  0:40 ` Joey Pabalinas
2018-09-03 14:02 ` Daniel Shahaf
2018-09-03 18:43   ` Joey Pabalinas
2018-09-17 20:13     ` Ben Klein [this message]
2018-09-17 20:46       ` Daniel Shahaf
2018-09-17 21:01         ` Mikael Magnusson
2018-09-17 21:20           ` Bart Schaefer
2018-09-17 21:19       ` dana
2018-09-17 21:33         ` Bart Schaefer
2018-09-18  5:12 ` Sebastian Gniazdowski
2018-09-21  6:58   ` Oliver Kiddle

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=cd8bc7e0-7ae1-8c94-8dea-9b529b2a8fb2@gmail.com \
    --to=robobenklein@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=joeypabalinas@gmail.com \
    --cc=zsh-users@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).