From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: The elements of enlightenment
Date: Tue, 6 Dec 2022 19:55:43 +0100 [thread overview]
Message-ID: <CAN=4vMp_LqvioJE_uW2_CwJ7CKL2dVwGn-6LMonPf_5pfngkzA@mail.gmail.com> (raw)
In-Reply-To: <37b2456f-0459-4b85-74d1-bb380715e2ed@eastlink.ca>
On Tue, Dec 6, 2022 at 12:53 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> I hafta wonder why this forking is so necessary.
It's necessary because it's user-visible. Some code relies on the PID
within $(...) to be different from the parent. This is mostly relevant
for signals. In addition, changes to parameters and other shell state
within $(...) have no effect on the parent shell, which doesn't
necessarily require forking but is made easier by it.
That said, it's totally possible to extend zsh with something like $[
... ] which would work like $( ... ) but without forking. It would run
the commands in another thread within the same process. The main
thread would be blocked on reading from the pipe until all commands
are executed.
Roman.
next prev parent reply other threads:[~2022-12-06 18:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 15:57 Ray Andrews
2022-12-05 16:24 ` Roman Perepelitsa
2022-12-05 18:30 ` Bart Schaefer
2022-12-05 19:35 ` Ray Andrews
2022-12-05 19:44 ` Bart Schaefer
2022-12-05 19:58 ` Roman Perepelitsa
2022-12-05 21:20 ` Ray Andrews
2022-12-05 21:49 ` Roman Perepelitsa
2022-12-05 23:52 ` Ray Andrews
2022-12-06 0:17 ` Bart Schaefer
2022-12-06 1:34 ` Ray Andrews
2022-12-06 18:55 ` Roman Perepelitsa [this message]
2022-12-06 19:45 ` Bart Schaefer
2022-12-06 20:01 ` Roman Perepelitsa
2022-12-06 20:07 ` Bart Schaefer
2022-12-06 20:22 ` Roman Perepelitsa
2022-12-06 23:52 ` Lawrence Velázquez
2022-12-07 1:04 ` Lawrence Velázquez
2022-12-05 21:49 ` Bart Schaefer
2022-12-05 21:51 ` Bart Schaefer
2022-12-05 22:24 ` Ray Andrews
2022-12-05 23:24 ` Bart Schaefer
2022-12-06 1:47 ` Ray Andrews
2022-12-06 6:39 ` Lawrence Velázquez
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='CAN=4vMp_LqvioJE_uW2_CwJ7CKL2dVwGn-6LMonPf_5pfngkzA@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=rayandrews@eastlink.ca \
--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).