From: Ben Klein <robobenklein@gmail.com>
To: zsh-users@zsh.org
Subject: Capturing STDOUT without subshells or file I/O
Date: Sun, 2 Sep 2018 16:57:49 -0400 [thread overview]
Message-ID: <04a12c6a-c926-b088-f386-8a2bdb81dad2@gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1404 bytes --]
Hello Zshellers,
I have an interesting predicament, I with to capture the STDOUT (builtin
printf) of a ZSH function to a variable, in which the function should be
running in the current shell context.
Currently, I have this:
p10k_render_prompt_from_spec p10k_left p10k_opts > $tmpd/prompt
read -d $'\0' _P10K_RENDERED_OUTPUT_PROMPT < $tmpd/prompt
p10k_render_prompt_from_spec p10k_right p10k_opts right > $tmpd/prompt
read -d $'\0' _P10K_RENDERED_OUTPUT_RPROMPT < $tmpd/prompt
And that involves creating a temporary file (/tmp) which might be
mounted on a spinning drive, so performance might take a hit.
The other route using a pipe:
p10k_render_prompt_from_spec p10k_left p10k_opts | read -d $'\0'
_P10K_RENDERED_OUTPUT_PROMPT
Causes environment variables and changes made during the `render_prompt`
call to be ignored. (Ends up in a subshell...?)
Is there some way I can use a virtual FD, or perhaps Zsh provides some
kind of buffer I could use instead?
In the end, I'm looking for a way to connect STDOUT to STDIN between ZSH
functions/builtins without any subshells or file I/O. (It's fine if it
gets buffered until close-of-stream.)
--
*\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: 2005 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next reply other threads:[~2018-09-02 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 20:57 Ben Klein [this message]
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
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=04a12c6a-c926-b088-f386-8a2bdb81dad2@gmail.com \
--to=robobenklein@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).