From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Eric Freese <ericdfreese@gmail.com>
Cc: Peter Stephenson <p.stephenson@samsung.com>,
Zsh Users <zsh-users@zsh.org>
Subject: Re: Anyone familiar with auto-fu.zsh project?
Date: Wed, 13 Jun 2018 09:27:56 +0200 [thread overview]
Message-ID: <CAKc7PVD-qcYmSDvisqf1Fea3Nw4DV-Ohe3UHSCST7WS4P=6Liw@mail.gmail.com> (raw)
In-Reply-To: <CAAikoAJYE=vyLUpwZcG4j85ENxqVVfRqDSFms1dOFUTzx52Pig@mail.gmail.com>
On 13 June 2018 at 06:09, Eric Freese <ericdfreese@gmail.com> wrote:
> It just occurred to me that, with zsh/system, I can have the child process
> send its pid as the first line of output.
>
> Something like:
>
> ```
> % zmodload zsh/system
> % exec {FOO}< <(echo $sysparams[pid]; sleep 100; echo foo bar)
> % read childpid <&$FOO # Get the pid, stored in $childpid
> % cat <&$FOO # Handle the rest of the output
> ```
Cool. <() processes are fun, such tricks make a day. I wonder if
someone has some <( ) tricks up in sleeve, broadening of horizons
might result in better code or even architecture.
--
Best regards,
Sebastian Gniazdowski
next prev parent reply other threads:[~2018-06-13 7:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 17:42 Sebastian Gniazdowski
2018-06-06 18:35 ` Eric Freese
2018-06-09 15:30 ` Sebastian Gniazdowski
2018-06-10 0:58 ` Eric Freese
2018-06-11 5:24 ` Sebastian Gniazdowski
2018-06-11 8:25 ` Eric Freese
2018-06-11 9:46 ` Sebastian Gniazdowski
2018-06-12 1:55 ` Eric Freese
2018-06-12 10:23 ` Sebastian Gniazdowski
2018-06-12 11:32 ` Peter Stephenson
2018-06-13 4:09 ` Eric Freese
2018-06-13 7:26 ` dana
2018-06-13 7:32 ` Sebastian Gniazdowski
2018-06-13 8:28 ` Sebastian Gniazdowski
2018-06-13 9:17 ` dana
2018-06-13 10:48 ` Sebastian Gniazdowski
2018-06-13 11:43 ` dana
2018-06-14 8:55 ` Peter Stephenson
2018-06-14 9:48 ` dana
2018-06-14 10:00 ` Peter Stephenson
2018-06-13 7:27 ` Sebastian Gniazdowski [this message]
2018-06-06 23:45 ` Takeshi Banse
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='CAKc7PVD-qcYmSDvisqf1Fea3Nw4DV-Ohe3UHSCST7WS4P=6Liw@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=ericdfreese@gmail.com \
--cc=p.stephenson@samsung.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).